Details
-
Task
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
4.0.0
-
None
Description
If we have some plan that contains scan with filter (or project) as parent, it can happen we want to do planning of scan using extra strategies instead of DataSourceV2Strategy.
One of use-cases:
Snowflake and BigQuery connectors have their own strategies and we want to prohibit DataSourceV2Strategy to do planning of scan node.
Despite the fact extra strategies have priority, it can happen that strategy fails to planĀ
Filter->Relation, but it can plan only Relation without its parent. In that case, DataSourceV2Strategy will jump in and it will be able to plan Filter->Relation in just one pass.
So we want to have ability to prevent that for certain Scan classes
Attachments
Issue Links
- links to