-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Optimize exception handling in GCP bigtable operator and hook #61124
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
base: main
Are you sure you want to change the base?
Optimize exception handling in GCP bigtable operator and hook #61124
Conversation
mentioned about deprication of project_id parameter
|
@shahar1 due to a small mistake i accidentally pushed the all commits and got auto assigned reviewers. Sorry for that. |
shahar1
left a comment
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.
Not bad!
Please fix according to the comments.
providers/google/src/airflow/providers/google/cloud/hooks/bigtable.py
Outdated
Show resolved
Hide resolved
|
And Also Shahar this we are using everywhere in the operator instead of that we can use |
You may encapsulate it in the hook where applicable |
|
Okay Sure |
… not used. in hooks test_bigtable.py
|
I have updated the code according to your comments. Please have a view. |
…in hooks/test_bigtable.py
|
@shahar1 all the CI checks have passed. your approval would be great here |
shahar1
left a comment
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.
Looks much better!!!
One last thing to do is to update all docstrings of the operators and hooks according to the changes (for example, "Raises google.api_core.exceptions.NotFound" is not relevant anymore for the modified operators)
|
Thanks Shahar for your review. |
|
I created an issue for that yesterday inorder to get your approval before opening a PR. Please have a look #61269 |
I wasn't talking about the documentation in After your changes this won't be true anymore (same goes for strings in the other methods). |
|
Oh Okay. I misunderstood it. Now I get it. I will update it |
|
BTW, I already created a branch and was working on it for #61269 seems it already got assigned. Never mind. Let the other person do the work :) |
Fixes #60687