boazberman commented on PR #5362: URL: https://github.com/apache/arrow-datafusion/pull/5362#issuecomment-1440351641
Hmm my approach to this (when trying to implement index usage) is a bit different different. I wrote an optimization rule to rewrite the query plan to use a different table. This is yet to be working (I have schema related errors), but I think it is at least worth throwing that into the discussion. In terms of best approach, I think it would be wise to a new physical plan node called `IndexScan` (like _TableScan_), to have a more meaningful query plans with `EXPLAIN`, and to make it closer to how OLTP databases present that data. -- 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]
