That method is intended if you have a class MyTableScan and a generic rule that
can handle any instance of MyTableScan.
If you have (say) five instances of MyTableScan and five rule instances, one
for each scan, then you should register each rule instance individually in the
planner.
There
Hello Calcite devs,
Our team currently has a setup in which we have a single TableScan
implementation (e.g. MyTableScan) serving multiple Calcite tables. Each
MyTableScan handles the registration of rules tailored to its respective
Calcite table. I've included an example of the code structure at
