Github user junegunn commented on the issue:
https://github.com/apache/spark/pull/16347
@chpritchard-expedia The patch here fixes the problem. I don't think it's
possible to workaround the issue by using Spark API in some different ways,
because we can't completely avoid memory spills at the writers. Hive doesn't
have the problem, so maybe you can consider running the same statement on Hive
if this is not something Spark wants to address.
Anyway, for anyone who's interested, I could confirm that for a sorted ORC
table built with this patch, point/range lookups on the sorted column can be
several times faster. Also the final size of the table turned out to be
significantly smaller in this case (60% of unsorted table) due to the temporal
locality in our data.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
