Uh oh!
There was an error while loading. Please reload this page.
HIVE-25497: Moving to ORC to 1.7.2 - #2853
Conversation
… a hard implementing its own TreeReaderFactory but initially we are going to avoid LAZY IO here as everything is kept in memory. Change-Id: I210d820efac97e2146dfebfb7d10942980124350
Change-Id: I0aaf22212270daf93dffdd0969e995da5a61b587
dongjoon-hyun
commented
Jan 12, 2022
Hi, @pgaref .
cc @williamhyun |
pgaref
commented
Jan 12, 2022
Hey @dongjoon-hyun -- thanks for checking! |
dongjoon-hyun
commented
Jan 12, 2022
Thank you for the info, @pgaref . |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
slachiewicz
commented
May 21, 2022
@kgyrtkirk@pgaref could reopen PR and review again? |
dongjoon-hyun
commented
May 21, 2022
+1 for @slachiewicz comment. The latest one is Apache ORC 1.7.4. We can re-try with 1.7.4. |
dongjoon-hyun
commented
May 21, 2022
And, FYI, cc @williamhyun and @stiga-huang |
What changes were proposed in this pull request?
Bumping to 1.7.1.
LLAP EncodedTreeReaderFactory is implementing its own TreeReaderFactory -- initially we are going to avoid LAZY IO here as everything is kept in memory.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?