There is class AbstractQueryable so you shouldn’t need to implement the whole
interface by hand.
However, a better next step after FilterableTable is not QueryableTable, but
Table with a few planner rules to push down filters, projects, etc. Calcite
gets its intelligence from how rules compose
Hello David,
AFAIK there is no such thing.
It might be interesting for your case to take a look at this presentation
[1], which includes a demo with the initial steps to combine Calcite and
Lucene.
Best,
Ruben
[1] https://youtu.be/meI0W12f_nw
El jue, 25 ene 2024, 1:55, escribió:
> Hello
Hello Calcite Devs,
I'm working on a data mocking system that's accessible via a relational
API: tables, columns, indexes, etc. I implemented a rudimentary query
runner layer from scratch, so the project is already usable in MVP
state. The next step would be the integration of Calcite.
For
