Description
Right now, we have a special place in the optimizer where we run rules for constructing v2 scans. As time shows, we need more rewrite rules for v2 tables and not all of them related to reads. One option is to rename the current batch into something more generic but it would require changing quite some places. Moreover, the batch contains some non-V2 logic as well. That's why it seems better to introduce a new batch and use it for all data source v2 rewrites and beyond.
Attachments
Issue Links
- is related to
-
SPARK-33784 Rename dataSourceRewriteRules and customDataSourceRewriteRules in BaseSessionStateBuilder
- Resolved
- relates to
-
SPARK-33621 Add a way to inject data source rewrite rules
- Resolved
- links to