- Notifications
You must be signed in to change notification settings - Fork126
Support for enforcing embedded schema#505
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
Conversation
src/databricks/sql/client.py Outdated
| self, | ||
| operation:str, | ||
| parameters:Optional[TParameterCollection]=None, | ||
| enforceEmbeddedSchema=False, |
jackyhu-dbFeb 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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.
can you rename it toenforce_embedded_schema_correctness to be consistent with the meaning of the thrift API. "enforce schema" is different with "enforce schema with correctness". And please use snake case which is python style.
72b0044 intorelease/v3.7.3Uh oh!
There was an error while loading.Please reload this page.
Description
As a part of query optimization Databricks returns cached results when the underlying query is the same. This creates issue when the same query is used but with a different alias, in this case the result is the same but the metadata is different. But Databricks returns the same metadata as a part of query optimisation
Added
Added option to enforce schema to make sure the metadata is in updated state