SNOW-1720855: clean up multithreading changes after rollout#2658
Conversation
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
…hanges-after-rollout
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
…hanges-after-rollout
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
…hanges-after-rollout
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
| _PYTHON_SNOWPARK_LARGE_QUERY_BREAKDOWN_COMPLEXITY_LOWER_BOUND = ( | ||
| "PYTHON_SNOWPARK_LARGE_QUERY_BREAKDOWN_COMPLEXITY_LOWER_BOUND" | ||
| ) | ||
| _PYTHON_SNOWPARK_ENABLE_THREAD_SAFE_SESSION = ( |
There was a problem hiding this comment.
do we need to clean up this parameter in the backend?
…hanges-after-rollout
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
sfc-gh-helmeleegy
left a comment
There was a problem hiding this comment.
This is increasing the number of query counts and join counts, etc in many tests. Do we know why?
|
Seems like your changes contain some Local Testing changes, please request review from @snowflakedb/local-testing |
I looked into the failed tests and the ones that are have |
The approach above was not as clean. I made the SqlCounter thread-safe now. |
sfc-gh-helmeleegy
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks!
…hanges-after-rollout
…hanges-after-rollout
…hanges-after-rollout
Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes SNOW-1720855
Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
Clean-up code by removing param protection and remove tests that test the case when thread-safe session is disabled.