Julian,
This needs a small refactoring, can you try to finish and benchmark it, try
to avoid casting and reflection as much you can. The test that is desirable
to see are:
- misure in milliseconds the performance introducing calcite:
1. a query without calcite.
2. a query with your calcite sup
2022 um 13:54
An: dev
Betreff: Re: Usage of Relation Algebra, Calcite and Query Optimization in IoTDB
Hi,
This is a good way to make the query processing clear.
> And in the next step, we could introduce INDEXES which in this scenario
could be simply “materialized views” with pre-cached resu
Hi,
This is a good way to make the query processing clear.
> And in the next step, we could introduce INDEXES which in this scenario
could be simply “materialized views” with pre-cached results that were
again stored as a table.
Does Calcite has frameworks for INDEXES? it beyonds my knowledge.
Hello Julian,
could you point out the branch? What about just including what you need of
Calcite?
Best Regards,
Giorgio.
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
