-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify Snowflake object name handling in the Snowpark AST #2789
Merged
Merged
Changes from 13 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
637f518
Update ast.proto
sfc-gh-oplaton 587b61f
Merge branch 'main' into oplaton/snow-1621205-object-name
sfc-gh-oplaton 12268b1
Update object name handling
sfc-gh-oplaton f9a657e
Stored procedure names
sfc-gh-oplaton a6c2515
Update table name handling
sfc-gh-oplaton 24c5033
Update AST test expectations
sfc-gh-oplaton 400eb39
Update ast.proto
sfc-gh-oplaton 2729b76
Merge branch 'main' into oplaton/snow-1621205-object-name
sfc-gh-oplaton ecc3923
Split functions.test into two files
sfc-gh-oplaton d592fcd
Merge branch 'main' into oplaton/snow-1621205-object-name
sfc-gh-oplaton 94822f6
Update ast.proto and use the new functionality
sfc-gh-oplaton 754bd65
Update expectation tests
sfc-gh-oplaton c67448f
Merge branch 'main' into oplaton/snow-1621205-object-name
sfc-gh-oplaton f5328e6
Merge branch 'main' into oplaton/snow-1621205-object-name
sfc-gh-oplaton 604c78e
Update AST expectation tests for temp table cleanup
sfc-gh-oplaton 4cf33fb
Merge branch 'main' into oplaton/snow-1621205-object-name
sfc-gh-oplaton File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these type-specific functions necessary? One thing I notice is that the re-emitted exceptions lose the diagnostic contents of the original exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's weird,
raise ... from ...
should preserve the contents. The functions aren't strictly necessary, but I find the call sites more readable (the name clarifies the intent), and the errors should have been more readable, too.