[
https://issues.apache.org/jira/browse/HIVE-25192?focusedWorklogId=627081&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-627081
]
ASF GitHub Bot logged work on HIVE-25192:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/21 09:33
Start Date: 23/Jul/21 09:33
Worklog Time Spent: 10m
Work Description: dengzhhu653 commented on a change in pull request #2473:
URL: https://github.com/apache/hive/pull/2473#discussion_r675430051
##########
File path: ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java
##########
@@ -2572,18 +2569,24 @@ public static ContentSummary getInputSummary(final
Context ctx, MapWork work, Pa
int numExecutors = getMaxExecutorsForInputListing(ctx.getConf(),
pathNeedProcess.size());
if (numExecutors > 1) {
Review comment:
The default value of `numExecutors` is 1 unless `pathNeedProcess.size()`
> 1 and `hive.exec.input.listing.max.threads` sets to the value bigger than 1.
We do not need the global lock when `numExecutors = 1`, and can be converted
to a finer-grained lock. In our cluster, we found that many handler threads
were blocked by the global lock when one of federation namespaces failover.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 627081)
Time Spent: 1h (was: 50m)
> Nullify summary for non-native tables
> -------------------------------------
>
> Key: HIVE-25192
> URL: https://issues.apache.org/jira/browse/HIVE-25192
> Project: Hive
> Issue Type: Bug
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When creating non-native tables like kudu, hbase and so on, we create a
> warehouse location for these tables, though these tables may not use the
> location to store data or for job plan, we should skip getting the input
> summary of non-native tables when optimising joins, as which may cause oom
> problem when the non-native table is on the build side.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
