-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Provide descriptive error on invalid table reference #1627
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
1a91a33
Initial commit to catch nonexistent table
da7a712
simplify nonexistent BQ table test
f6a2f98
clean up table_exists exception
41e69a7
remove unneeded variable
af937c4
function name change to _assert_table_exists
215de4b
Initial commit to catch nonexistent table
caac9d0
simplify nonexistent BQ table test
2d2a484
clean up table_exists exception
c548ab6
function name change to _assert_table_exists
d5eb8af
fix lint errors and rebase
21a7631
Fix get_table(None) error
50831ef
custom exception for both missing file and BQ source
4e7a803
revert FileSource checks
2d99b05
Use DataSourceNotFoundException instead of subclassing
c513660
Moved assert_table_exists out of the BQ constructor to apply_total
617dde1
rename test and test asset
6b3975a
move validate logic back to data_source
458beab
fixed tests
5abc428
Set pytest.integration for tests that access BQ
4ec510d
Import pytest in failed test files
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
custom exception for both missing file and BQ source
Signed-off-by: Cody Lin <codyl@twitter.com>
- Loading branch information
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
I'm not sure if it's a good idea to have implementation specific errors. We are moving to having all implementations be self-contained. Any downside to using
DataSourceNotFoundExceptioninstead of subclassing?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.
Ah thanks for letting me know - I was following the example of the
FeastObjectNotFoundExceptionsubclassing pattern here, but since theDataSourceNotFoundExceptions are so similar (and we're not checkingFileSourceyet), I'll just change it to useDataSourceNotFoundExceptioninstead.