Add config option to enable case-insensitive column lookup #164
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
danielcweeks
approved these changes
Nov 23, 2023
bryanck
force-pushed
the
case-insensitive-col-lookup
branch
from
7cd1c89 to
7a2ee08
Compare
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.
During conversion from Kafka record to Iceberg record, fields are matched based on the field name in the schema. Currently the field name lookup in the schema is case-sensitive. This PR adds the config option
iceberg.tables.schema-case-insensitiveto allow this lookup to be case-insensitive.Note that lookups can also use Iceberg's name mapping feature, and this is still always case-sensitive.