hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HIVE-15881) Use new thread count variable name instead of mapred.dfsclient.parallelism.max
Date Mon, 13 Feb 2017 23:44:41 GMT

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

Sergio Peña commented on HIVE-15881:
------------------------------------

Thanks guys for giving more ideas. [~etf] I like that idea of the "max.threads" option. I
will implement it in that way to avoid creating a threadpool with more threads than the number
of input locations.

[~poeppt] I like those names better. I wonder if we should have 1 variable config for both
instead of one per method. Don't you guys get messy with too many configurations variables
for the number of threads?

> 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
>
> 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)

Mime
View raw message