Use resultFormat
field to properly process query results
#92
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
getResultSetMetadata
has aresultFormat
field that should be used to determine a format of query result. Previously we alway tried to process results asCOLUMN_BASED_SET
, but here are few reasons to finally use that field:ARROW_BASED_SET
) - see also corresponding part in PySQL connector https://github.com/databricks/databricks-sql-python/blob/f99123cde1ee431f364286fa12f3f42fb859d56e/src/databricks/sql/thrift_backend.py#L707-L710ROW_BASED_SET
data. This PR doesn't add a parser for that format though, but at least now users will get a meaningful error