-
Notifications
You must be signed in to change notification settings - Fork 112
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SNOW-1632896] Detect valid condition for flatten nested select proje…
…ction complexity (#2326) <!--- Please answer these questions before creating your pull request. Thanks! ---> 1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR. <!--- In this section, please add a Snowflake Jira issue number. Note that if a corresponding GitHub issue exists, you should still include the Snowflake Jira issue number. For example, for GitHub issue #1400, you should add "SNOW-1335071" here. ---> NOW-1632896 2. Fill out the following pre-review checklist: - [x] I am adding a new automated test(s) to verify correctness of my new code - [ ] If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing - [ ] I am adding new logging messages - [ ] I am adding a new telemetry message - [ ] I am adding new credentials - [ ] I am adding a new dependency - [ ] If this is a new feature/behavior, I'm adding the Local Testing parity changes. 3. Please describe how your code solves the related issue. snowflake optimization can merge the select statement when possible, to get a more accurate estimation of the query plan complexity, we want to detect such case and adjust the complexity calculation. For example, SELECT COL1 + 2 AS COL1, COL2 FROM (SELECT COL1 + 1 AS COL1, COL2 FROM TEST_TABLE) can be merged as SELECT (COL1 + 1) + COL1 + 2 AS COL1, COL2 FROM TEST_TABLE. A parameter _try_merge_projection_complexity is added to SelectStatement to indicate that we should try to merge the select projection complexity with the child (from).
- Loading branch information
1 parent
272e4e1
commit 965ce9d
Showing
3 changed files
with
543 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.