[
https://issues.apache.org/jira/browse/HIVE-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851936#comment-15851936
]
Pengcheng Xiong commented on HIVE-15803:
----------------------------------------
If I remembered correctly, I did not share the thread pool when I do a BFS in
my first patch. Then reviewers suggested reuse the thread pool. I changed my
patch to reuse them. If we are using the patch here, then it means we are only
using thread-pool for the first level of directory. I think this is a setting
problem. I would suggest that the user should set hive.mv.files.thread=0 or
hive.mv.files.thread=a number that is large enough. Or i would change
hive.mv.files.thread to a boolean. If it is true, then we are going to
automatically set it to the maximum number, else we set it to 0. How about
this? ccing [~ashutoshc] and [~hagleitn]
> msck can hang when nested partitions are present
> ------------------------------------------------
>
> Key: HIVE-15803
> URL: https://issues.apache.org/jira/browse/HIVE-15803
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Priority: Minor
>
> Steps to reproduce.
> {noformat}
> CREATE TABLE `repairtable`( `col` string) PARTITIONED BY ( `p1` string,
> `p2` string)
> hive> dfs -mkdir -p /apps/hive/warehouse/test.db/repairtable/p1=c/p2=a/p3=b;
> hive> dfs -touchz
> /apps/hive/warehouse/test.db/repairtable/p1=c/p2=a/p3=b/datafile;
> hive> set hive.mv.files.thread;
> hive.mv.files.thread=15
> hive> set hive.mv.files.thread=1;
> hive> MSCK TABLE repairtable;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
