[SPARK] Stringify the delta optimize 'auto' operationalParameter in CommitInfo #3889
+21
−13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eter' in CommitInfo
MaicoTimmerman
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which Delta project/connector is this regarding?
Description
The
inCommitTimestampfeature of Delta Kernel API expects theoperationalParametersofCommitInfoto be aMapType<StringType, StringType>.The newly added
autoCompactfeature added theautoflag tooperationalParamatersas a boolean, which is incompatible.This PR restores that expectation of the
inCommitTimestampfeature for theOPTIMIZEoperation in the Spark Connector.Resolves #3888.
How was this patch tested?
I've attached a test-case.
Does this PR introduce any user-facing changes?
We change format of the field
commitInfo.operationalParameters.autofield from boolean to string.