[jira] [Comment Edited] (HIVE-15881) Use new thread count variable name instead of mapred.dfsclient.parallelism.max

["Thomas Poepping (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-15881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876900#comment-15876900 ] 

Thomas Poepping edited comment on HIVE-15881 at 2/21/17 10:42 PM:
------------------------------------------------------------------

Hey [~spena], updated the RB. Just one question, otherwise non-binding +1 pending QA 


was (Author: poeppt):
Hey [~spena], updated the RB. Just one question, otherwise non-binding +1

> Use new thread count variable name instead of mapred.dfsclient.parallelism.max
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-15881
>                 URL: https://issues.apache.org/jira/browse/HIVE-15881
>             Project: Hive
>          Issue Type: Task
>          Components: Query Planning
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>            Priority: Minor
>         Attachments: HIVE-15881.1.patch, HIVE-15881.2.patch
>
>
> The Utilities class has two methods, {{getInputSummary}} and {{getInputPaths}}, that use the variable {{mapred.dfsclient.parallelism.max}} to get the summary of a list of input locations in parallel. These methods are Hive related, but the variable name does not look it is specific for Hive.
> Also, the above variable is not on HiveConf nor used anywhere else. I just found a reference on the Hadoop MR1 code.
> I'd like to propose the deprecation of {{mapred.dfsclient.parallelism.max}}, and use a different variable name, such as {{hive.get.input.listing.num.threads}}, that reflects the intention of the variable. The removal of the old variable might happen on Hive 3.x



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)