-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Exclude partition from BigQuery table name #42130
Exclude partition from BigQuery table name #42130
Conversation
ac83431
to
6460d9d
Compare
Please enter the commit message for your changes. Lines starting
6460d9d
to
7384f33
Compare
I think I have discovered an issue with this commit that is affecting tasks that use the Results in an error like this.
I will dig into it more tomorrow and hopefully have a fix for it ASAP. |
@moiseenkov Why are we excluding the partition from the table_id? |
The reason was that partitioning breaks integration of this operator with Google Cloud Dataplex when it is launched in Cloud Composer. Apparently, my fix introduced another bug, so we should probably revert it. Regarding the initial problem with integration, I think we can take care of it on the Cloud Composer's side. Sorry for troubling. |
@moiseenkov No worries. It's not your fault. We should have better test coverage. Do you want to revert it? |
This PR contains one valuable deprecation which we'd like to keep. Thus we will introduce another PR that only reverts the breaking changes. |
Sounds good! I will actually look at adding a test to the |
Thanks! |
Please enter the commit message for your changes. Lines starting
split_tablename
which is identical to the methodBigQueryHook.split_tablename
.