RANGER-5125: Missing accessResult column value in ORC File Logging #524
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.
What changes were proposed in this pull request?
short
values (e.g.,accessResult
field) were not correctly converted to strings before being written to ORC.castStringObject(Object object)
to properly handleShort
values by converting them to strings.Why is this needed?
short
values were missing from the ORC output because they were not handled incastStringObject()
, leading to incorrect (empty) values in the ORC file.short
values are correctly converted to strings before being stored in ORC.How was this patch tested?
main()
method fromOrcUtils.java
.