[
https://issues.apache.org/jira/browse/HIVE-25335?focusedWorklogId=771879&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-771879
]
ASF GitHub Bot logged work on HIVE-25335:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/22 13:40
Start Date: 18/May/22 13:40
Worklog Time Spent: 10m
Work Description: zabetak commented on PR #3292:
URL: https://github.com/apache/hive/pull/3292#issuecomment-1130032347
@zhengchenyu I am not sure what exactly do you mean by saying the unit tests
are working in your environment. If you check the failed tests you will see a
lot related to the `TestMiniLlapLocalCliDriver`. If you want to run these tests
and update the plans you don't need Jenkins or anything else. You can do it by
following the steps below:
```
mvn clean install -DskipTests -Pitests
cd itests/qtest
mvn test -Dtest=TestMiniLlapLocalCliDriver -Dtest.output.overwrite
```
If you want to run specific tests then you can use the `-Dqfile` option. For
more info have a look here:
https://cwiki.apache.org/confluence/display/Hive/HiveDeveloperFAQ#HiveDeveloperFAQ-HowdoIruntheclientpositive/clientnegativeunittests?
Issue Time Tracking
-------------------
Worklog Id: (was: 771879)
Time Spent: 3h (was: 2h 50m)
> Unreasonable setting reduce number, when join big size table(but small row
> count) and small size table
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-25335
> URL: https://issues.apache.org/jira/browse/HIVE-25335
> Project: Hive
> Issue Type: Improvement
> Reporter: zhengchenyu
> Assignee: zhengchenyu
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-25335.001.patch
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> I found an application which is slow in our cluster, because the proccess
> bytes of one reduce is very huge, but only two reduce.
> when I debug, I found the reason. Because in this sql, one big size table
> (about 30G) with few row count(about 3.5M), another small size table (about
> 100M) have more row count (about 3.6M). So JoinStatsRule.process only use
> 100M to estimate reducer's number. But we need to process 30G byte in fact.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
