add config parse_hex_as_fixed_size_binary #15687
Closed
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
github-actions
bot
added
sql
leoyvens
force-pushed
the
parse_hex_as_fixed_size_binary
branch
2 times, most recently
from
b6366ad to
72dc068
Compare
github-actions
bot
added
the
documentation
leoyvens
force-pushed
the
parse_hex_as_fixed_size_binary
branch
from
72dc068 to
adda058
Compare
leoyvens
force-pushed
the
parse_hex_as_fixed_size_binary
branch
from
adda058 to
540ca95
Compare
Contributor
|
I have an alternate suggestion here: #15686 (comment) |
Contributor
|
I believe we went with an alternate approach in |
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.
Which issue does this PR close?
What changes are included in this PR?
Adds
parse_hex_as_fixed_size_binaryparser option.Are these changes tested?
There is an SLT test.
Are there any user-facing changes?
The configuration defaults to
false, no breaking change. I'm not sure if docs updates are required.