> . For rules tagged as “single-convention”, we could add some support in the > engine to reduce the burden on the person writing the rule The issue is current rules are broken, and it would be nice to fix that without having to rewrite each and every rule.
>categorize rules as “converters” It makes sense to categorize rel classes as well. For instance, LogicalProject'a input should always be Convention.NONE. Then Calcite could raise an error when LogicalProject(EnumerableFilter(..)) is created. Vladimir
