SEA parameters fix: pass params as ttypes.TSparkParameter
to re-use existing parameter processing
#612
+7
−5
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.
What type of PR is this?
Description
Earlier,
execute_command
inSeaDatabricksClient
was expecting aList[Dict[str, Any]]
, with the intention of implementing parameter processing later and converting them into a simpleList[Dict]
to be consumed by the SEA backend.But, this does not align with the current code which passes a
List[ttypes.TSparkParameter]
. Also, re-using this Thrift parameter object allows us to re-use the existing parameter processing completely.How is this tested?
"use_sea": True
in theconnection params
Related Tickets & Documents
N/A