[core] fix the wrong parsing for map type with string sub type #6790
+50
−2
Conversation
This file contains hidden or 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
JingsongLi
reviewed
Dec 10, 2025
| } | ||
|
|
||
| private List<String> splitMapEntries(String content) { | ||
| public List<String> splitMapEntries(String content) { |
Contributor
There was a problem hiding this comment.
Maybe we can introduce something like Spark CollationAwareUTF8String.splitSQL.
Contributor
Author
There was a problem hiding this comment.
Let's research it, but can we deal with it with this tiny change?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose
col MAP<BIGINT, STRING> DEFAULT map(9999, "hello")Without this pr, this value part of the default value is
"hello", but it should behello.Tests
API and Format
Documentation