- Notifications
You must be signed in to change notification settings - Fork321
fix:query_and_wait now retains unknown query configuration_properties#1793
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
query_and_wait now retains unknown query configuration `_prope…query_and_wait now retains unknown query configuration_propertiesLinchin commentedJan 19, 2024
Could you tell me more about the rationale of keeping unknown config fields? |
tswast commentedJan 22, 2024
Two reasons: (1) as you can see from the removal of this code: it allows for a cleaner conversion from query job insert request to jobs.query request. (2) It allows for customers who want access to features that are in preview an not yet implemented in the client library to set REST API properties via setting |
Linchin commentedJan 23, 2024
That's great to know! Thank you |
Uh oh!
There was an error while loading.Please reload this page.
fix: raise
ValueErrorinquery_and_waitwith wrongjob_configtypeThank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes#1792
🦕