I don't mean to fire a Volcano rule. I mean to just reuse the code in a creative way for the purpose of SqlUserDefinedTableMacro.coerce
Currently, SqlUserDefinedTableMacro.coerce knows certain hard-coded cases, however it would probably be better if the conversion could be just reused from already existing in Calcite code. Vladimir
