dennis zhuang
dennis zhuang
Right now the HTTP timeout value is hard coded in https://github.com/GreptimeTeam/greptimedb/blob/develop/src/servers/src/http.rs#L316 We should add an option to configure it. ## TODO - [ ] Adds the timeout option to `FrontendOptions`...
Bulk load data from sources, such as: * csv file * json file * parquet file * other tables * mysql table * ....
For debug or observerbility, we should add more metrics to: * table-engine(mito) * storage engine * servers(datanode and frontend etc.) * slow query
If we want to query data written by prometheus via SQL ,we have to impl a rate funciton just like [rate()](https://prometheus.io/docs/prometheus/latest/querying/functions/#rate) in prometheus.
The backend is already ready, but we have to impl them in SQL.
Start the frontend by `cargo run -- frontend start`, it fails with error: ``` 2022-10-19T06:53:12.655693Z ERROR greptime: Fatal error occurs! err.msg=Failed to start frontend, source: Failed to connect Datanode at...
When there were many tables( over 200 for example), the datanode startup too slowly(nearly half of a minute). I think we should turn this performance by opening table in parallel...
When we query from a metrics table written by prometheus remote write: ``` select * from prometheus_tsdb_head_min_time order by greptime_timestamp; +---------------------+---------------------+----------------+------------+ | greptime_timestamp | greptime_value | instance | job |...
When calling a python script,there were some log looks strange: ``` 022-09-08T02:45:40.549040Z INFO rustpython_vm::frame: Exception raised: PyBaseException with cause: None 2022-09-08T02:45:40.563370Z WARN rustpython_vm::object::core: couldn't run __del__ method for object 2022-09-08T02:45:40.563434Z...
* [ ] region manifest checkpoing * [ ] table manifest checkpoint