BUILD-FAILURE: Job 'IoTDB/IoTDB-Pipe/master [master] [447]':
Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/447/";>IoTDB/IoTDB-Pipe/master
[master] [447]"
BUILD-FAILURE: Job 'IoTDB/IoTDB-Pipe/master [master] [448]':
Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/448/";>IoTDB/IoTDB-Pipe/master
[master] [448]"
BUILD-FAILURE: Job 'IoTDB/IoTDB-Pipe/master [master] [449]':
Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/449/";>IoTDB/IoTDB-Pipe/master
[master] [449]"
BUILD-FAILURE: Job 'IoTDB/IoTDB-Pipe/master [master] [450]':
Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/450/";>IoTDB/IoTDB-Pipe/master
[master] [450]"
Hi folks,
I did some discussions already with others but wanted to bring the topic now to
the list.
Currently, we have no “real” Query Optimizer in IoTDB.
We do some heuristics to optimize queries but not in the way a regular RDBMS
does things.
Some of you may have heard of the Apache Calcite F
Hi folks,
I did some discussions already with others but wanted to bring the topic now to
the list.
Currently, we have no “real” Query Optimizer in IoTDB.
We do some heuristics to optimize queries but not in the way a regular RDBMS
does things.
Some of you may have heard of the Apache Calcite F
