The plan seems reasonable to me so as you said there seems to be a problem
with the Interpreter.
Overriding childrenAccept seems like a good workaround but I think it would
be nice to fix the Interpreter.
Can you please log a JIRA issue for this?
As a general remark, I don't use Bindable
Thank you all for your time but unfortunately I'm unable to overcome this
challenge so far. Allow me to explain more.
*This is how I'm using calcite*
Planner planner = Frameworks.getPlanner(frameworkConfig); //
frameworkConfig is irrelevant I suppose
SqlNode parsed = planner.parse("SELECT Tenant
Hi Muhammad,
I'm not sure why you need to implement InterpretableRel interface. I'm
probably missing some details.
I suppose you are using Calcite through the JDBC interface thus I guess you
are relying on CalcitePrepareImpl.
If that's the case then using TranslatableTable interface seems like a
You can set up the target traits to include the convention you want when invoke
the Program#run method [1], with the converters as rules of the program.
[1]
I implemented a new convention but I'm facing difficulties with
implementing tables for that convention.
Since I need to apply my convention rules and converters, I assume I must
implement TranslatableTable so I can override the RelNode produced by the
toRel method and provide the rules I need
