-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Google Display & Video 360 operators fail on POST requests #10076
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Thanks @echom for the issue! I will take a look at it :) |
Apologies, I posted the wrong log file from an old Orchestra implementation. Just updated to the correct log file, the error is the same. |
@echom if you know how to fix the issue would you like to do this? |
Hm, interesting because I run this operator from out example DAG:
and it seems to be working |
Which version of google libraries do you use?
|
I am running on Google Cloud Composer 1.10.6. According to their versioning: google-api-core==1.16.0 Let me try to explicitly install your versions. |
Ok, after a bit of a struggle with version issues I now arrived at the following: httplib2==0.18 Still the issue persists. @turbaszek Can you do me a favor and check if the API responds with a 303 for you? You should be able to get the response logged when I have a line in my log that looks like this:
|
No 303 on my side. However, this seems to be related: |
#8810 is closed. Should this item be closed as "no repro"? |
Closing as can't reproduce. If issue still relevant please open a new issue. |
Apache Airflow version: airflow-1.10.6
Kubernetes version (if you are using kubernetes) (use
kubectl version
): 1.18.6Environment: Google Cloud Composer v1.10.0
httplib2 >= 0.18
apache-airflow-backport-providers-google >= 2020.6.24
What happened:
airflow.providers.google.marketing_platform.operators.display_video.GoogleDisplayVideo360RunReportOperator
as well asairflow.providers.google.marketing_platform.operators.display_video.GoogleDisplayVideo360CreateReportOperator
fail to complete when setting theapi_version
parameter to the current versionv1.1
instead of the default (and now deprecated)v1
. In both cases the POST request return a redirect HTTP code (303) without aLocation
header. Full error message log (note that httplib2 debug output is enabled): log.txtWhat you expected to happen: Both operators should execute successfully.
What do you think went wrong?: I believe that there different interpretations of the HTTP 303 code between the DV360 API and httplib2. Httplib2 tries to follow the 303 redirect but fails due to the missing location header. I believe the implementation of httplib2 is correct, however, the DV360 operators need to handle the arguably invalid response and interpret it as a successful operation with no result. I was able to work around it by temporarily disabling
follow_redirects
on the service object inside theGoogleDisplayVideo360Hook
while the POST requests where executed.How to reproduce it:
Run either of the operators, e.g.:
Anything else we need to know:
How often does this problem occur? Once? Every time etc?: Every time
The text was updated successfully, but these errors were encountered: