kadinrabo opened a new issue, #23927: URL: https://github.com/apache/datafusion/issues/23927
DataFusion's Substrait consumer doesn't handle `ReadRel.ExtensionTable` today. That means custom table reads need to go through `ExtensionLeaf`, even when the Substrait plan is modeling a read. I think `ExtensionTable` should have a resolver hook that returns a DataFusion `LogicalPlan`, with the normal `ReadRel` filter/projection handling applied around the resolved plan. Substrait evaluates `ReadRel.filter` before `ReadRel.projection`, so that ordering matters here: https://substrait.io/relations/logical_relations/#read-filtering There may be room to reuse more of the named-table path, but I think this should preserve the existing named-table lowering for compatibility and only generalize the parts needed for non-named reads. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
