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.
Problem
Many Logical types don't work when writing ORC.
And when a hierarchal Record comes through, logical types are ignored entirely (convertPrimitiveMaybeLogical() is never called during recursive traversal), including DECIMAL.
Bug where hierarchal (not flattened) Kafka Connect records aren't converted to OrcStructs correctly.
Solution
Code changes to identify and serialize Kafka Connect Logical Types correctly, for: Date, Time and Timestamp and Decimal.
By default, parse all Logical types.
This PR should not be merged directly, and the following things need to be done:
Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan