bugfix - prevent table parameter duplication in Snowflake options dictionary #190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed an issue in
SnowflakeBaseModel.get_options()
where the 'table' parameter was being included in the options dictionary, causing conflicts in nested operations - likeAddColumn
- during schema synchronization. The fix excludes the table parameter while maintaining proper parameter handling for Snowflake connections, ensuring that operations can properly cascade options without parameter conflicts.The implementation also improves overall parameter handling across the Snowflake and JDBC reader classes while maintaining backwards compatibility.
Related Issue
closes #188
How Has This Been Tested?
New test has been added to cover for this scenario
Types of changes
Checklist: