[
https://issues.apache.org/jira/browse/HIVE-26088?focusedWorklogId=749943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-749943
]
ASF GitHub Bot logged work on HIVE-26088:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Mar/22 08:57
Start Date: 30/Mar/22 08:57
Worklog Time Spent: 10m
Work Description: lklong opened a new pull request #3150:
URL: https://github.com/apache/hive/pull/3150
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA:
https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description, screenshot and/or a reproducable
example to show the behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Hive versions or within the unreleased branches such as master.
If no, write 'No'.
-->
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
-->
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 749943)
Remaining Estimate: 0h
Time Spent: 10m
> a left join b left join c when b is null ，then b join c is null , in this
> case when set hive.auto.convert.join=true ; map join is not used ,because
> nullpointexecption
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-26088
> URL: https://issues.apache.org/jira/browse/HIVE-26088
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.1.2
> Reporter: lkl
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> create database pr;
> use pr;
>
> create table t1(id int,name string) PARTITIONED BY (cls string) stored as orc;
> create table t2(id int,name string) PARTITIONED BY (cls string) stored as orc;
> create table t3(id int,name string) PARTITIONED BY (cls string) stored as orc;
> insert into table t1 partition(cls=1) values(1,"zzz");
> insert into table t3 partition(cls=1) values(1,"zzz");
>
> sql:
> select y1.id,y1.name,nvl(y2.id,"其他") as y2id ,nvl(y2.name,"其他") as y2name
> from
> (select t1.id,t1.name from t1) y1
> left join
> (
> select a.id,a.name ,b.id as bid,b.name as bname from
> (select t2.id,t2.name from t2) a
> left join
> (select t3.id,t3.name from t3) b
> on a.id = b.id
> )y2
> on y1.id=y2.id;
>
> log msg：
> No Stats for mapjoin@t1, Columns: name, id
> No Stats for mapjoin@t3, Columns: id
> Query ID = hadoop_20220330164204_2a822fd5-7630-43f9-929a-b95086df04bf
> Total jobs = 3
> 2022-03-30 16:42:11 Starting to launch local task to process map join;
> maximum memory = 3817865216
> 2022-03-30 16:42:12 Uploaded 1 File to:
> file:/data/emr/hive/tmp/23201dda-9c15-4d6e-9904-12ae28d4dccb/hive_2022-03-30_16-42-04_837_944561186926371473-2/-local-10007/HashTable-Stage-6/MapJoin-mapfile30--.hashtable
> (278 bytes)
> Execution completed successfully
> MapredLocal task succeeded
> Launching Job 1 out of 3
> Number of reduce tasks is set to 0 since there's no reduce operator
> Starting Job = job_1646126523394_0063, Tracking URL =
> http://172.21.64.46:5004/proxy/application_1646126523394_0063/
> Kill Command = /usr/local/service/hadoop/bin/mapred job -kill
> job_1646126523394_0063
> Hadoop job information for Stage-6: number of mappers: 0; number of reducers: > 0
> 2022-03-30 16:42:18,781 Stage-6 map = 0%, reduce = 0%
> Ended Job = job_1646126523394_0063
> Stage-7 is filtered out by condition resolver.
> Stage-1 is selected by condition resolver.
> Launching Job 2 out of 3
> Number of reduce tasks not specified. Estimated from input data size: 1
> In order to change the average load for a reducer (in bytes):
> set hive.exec.reducers.bytes.per.reducer=<number>
> In order to limit the maximum number of reducers:
> set hive.exec.reducers.max=<number>
> In order to set a constant number of reducers:
> set mapreduce.job.reduces=<number>
> Starting Job = job_1646126523394_0064, Tracking URL =
> http://172.21.64.46:5004/proxy/application_1646126523394_0064/
> Kill Command = /usr/local/service/hadoop/bin/mapred job -kill
> job_1646126523394_0064
> Hadoop job information for Stage-1: number of mappers: 2; number of reducers:
> 1
> 2022-03-30 16:42:26,673 Stage-1 map = 0%, reduce = 0%
> 2022-03-30 16:42:30,768 Stage-1 map = 50%, reduce = 0%, Cumulative CPU 1.39
> sec
> 2022-03-30 16:42:31,792 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 2.92
> sec
> 2022-03-30 16:42:36,886 Stage-1 map = 100%, reduce = 100%, Cumulative CPU
> 4.83 sec
> MapReduce Total cumulative CPU time: 4 seconds 830 msec
> Ended Job = job_1646126523394_0064
> MapReduce Jobs Launched:
> Stage-Stage-6: HDFS Read: 0 HDFS Write: 0 SUCCESS
> Stage-Stage-1: Map: 2 Reduce: 1 Cumulative CPU: 4.83 sec HDFS Read:
> 15362 HDFS Write: 131 SUCCESS
> Total MapReduce CPU Time Spent: 4 seconds 830 msec
> OK
> 1 zzz 其他 其他
> Time taken: 33.102 seconds, Fetched: 1 row(s)
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
