[
https://issues.apache.org/jira/browse/HIVE-22964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051983#comment-17051983
]
Aditya Shah commented on HIVE-22964:
------------------------------------
Hi [~pvary], thanks for reviewing.
For Conf reuse, I was thinking of reusing "HIVE_ORC_COMPUTE_SPLITS_NUM_THREADS"
and renaming it to "HIVE_COMPUTE_SPLITS_NUM_THREADS". Should that be fine?
Also, for the second point are you referring to shutting down and canceling
futures in case one of the thread fails? I have done some handling for that
case. Am I understanding it correctly?
> MM table split computation is very slow
> ---------------------------------------
>
> Key: HIVE-22964
> URL: https://issues.apache.org/jira/browse/HIVE-22964
> Project: Hive
> Issue Type: Improvement
> Reporter: Aditya Shah
> Assignee: Aditya Shah
> Priority: Major
> Attachments: HIVE-22964.patch
>
>
> Since for MM table we process the paths prior to inputFormat.getSplits() we
> end up doing listing on the whole table at once. This could be optimized.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
