horaedb
horaedb copied to clipboard
apache
Apache HoraeDB (incubating) is a high-performance, distributed, cloud native time-series database.
**Description** Support for SQL is very important, but it is far from perfect in ceresdb now. Now there are some deficiencies as follow: + Tests are not enough. + SQL...
**Describe this problem** UT/CI sometimes is failed with "pure virtual method called, terminate called without an active exception" Two cases failed in my env are ```plaintext FAIL [ 0.353s] analytic_engine...
**Description** Some cases are not expected to run due to unstable features, temporary changes or anything else. It should be supported to just ignore them. **Proposal** Implement the `ignore` interceptor....
**Description** Support queries like ```sql select "string literal"; ``` Current the execution result is ``` SELECT 'a'; Failed to execute query, err: Client("Failed to parse schema from JSON") ``` **Proposal**...
**Describe this problem** Currently, select function(scalar) will return err like ``` Failed to execute query, err: Server(ServerError { code: 500, msg: "Failed to execute interpreter, query: SELECT NOT(1);. Caused by:...
**Description** Currently, `show tables` is supported by CeresDB, it would be convenient to support name like syntax like in MySQL. ``` SHOW TABLES LIKE 'pattern' ``` **Proposal** Support this syntax...
**Description** The query interface now supports avro and json format. https://github.com/CeresDB/ceresdb/blob/f6c9a5b03e23b04e6a06c4f73756f1be9551c0f8/server/src/grpc/query.rs#L42-L45 And avro is the only one actually used. Regardless of json, it's natural to support arrow (in arrow's [ipc...
**Description** In some scenarios where CeresDB servers are not accessible for client nodes because of the network isolation, the current end-to-end communications won't work any more. **Proposal** Make the CeresDB...
I've run `cargo build --release -Ztimings` and here is what I get: ------- - Top 10 Unit | Total | Codegen | Features -- | -- | -- | --...
**Description** When I was debugging, I found that the stack information of the exception often could not locate the real exception occurrence point. **Proposal** **Additional context** when i debugging this...
