> sargs That is an interesting part of a config. Am I right SargFactory is to "figure out which expressions can be pushed down in terms of simple conditions"?
However I guess some notion of "supported set of features" is required. For instance, Eclipse MAT does not support range scans. Just "unique scans". Current "boolean simpleMode" is too restrictive: it does not allow to enable ORs but disable range predicates. >That would be a useful exercise. I would be curious what you find works best. It looks like I have two options to represent my "index" table in model: 1) Table function 2) ProjectableFilterableTable As I tried the first approach I found this area is not yet explored: 1.1) Left correlation of table function does not work: select * from emp e, table(calc_dept(e.deptno) t https://issues.apache.org/jira/browse/CALCITE-463 1.2) If I rewrite it as lateral expression, then it fails in runtime: cannot translate expression $cor0.c at net.hydromatic.optiq.rules.java.RexToLixTranslator.translate0 https://issues.apache.org/jira/browse/CALCITE-462 Will try to go with EnumeratorCorrelatorRel first and look into the left-corellation/lateral issues later (hopefully after renaming is done). Vladimir
