[ 
https://issues.apache.org/jira/browse/HIVE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Capriolo resolved HIVE-22.
---------------------------------

    Resolution: Won't Fix

{noformat}
[med...@rs01 ~]$ cat a.txt
1ed
2stacey
[med...@rs01 ~]$ cat b.txt
1car
1dog

[med...@rs01 ~]$ hive
Hive history file=/tmp/media6/hive_job_log_media6_201012241700_1296890727.txt
hive> create table a (id int, name string);
OK
Time taken: 2.118 seconds
hive> create table b (id int, toy string);
OK
Time taken: 0.035 seconds
hive> load data locan infile 'a.txt' into a;
FAILED: Parse Error: line 1:10 mismatched input 'locan' expecting INPATH in 
load statement

hive> load data location infile 'a.txt' into a;
FAILED: Parse Error: line 1:10 mismatched input 'location' expecting INPATH in 
load statement

hive> load data local inpath 'a.txt' into a;   
FAILED: Parse Error: line 1:36 mismatched input 'a' expecting TABLE in load 
statement

hive> load data local inpath 'a.txt' into table a;
Copying data from file:/home/media6/a.txt
Loading data to table a
OK
Time taken: 0.212 seconds
hive> load data local inpath 'b.txt' into table b;
Copying data from file:/home/media6/b.txt
Loading data to table b
OK
Time taken: 0.128 seconds
hive> select * from a;
OK
1       ed
2       stacey
Time taken: 0.186 seconds
hive> from a join b on (a.id=b.id) select a.*,b.id where a.id>0;
Total MapReduce jobs = 1
Launching Job 1 out of 1
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 mapred.reduce.tasks=<number>
Starting Job = job_201011022322_0370, Tracking URL = 
http://rs01.hadoop.pvt:50030/jobdetails.jsp?jobid=job_201011022322_0370
Kill Command = /opt/hadoop-0.20-shell-dev/bin/hadoop job  
-Dmapred.job.tracker=rs01.hadoop.pvt:34311 -kill job_201011022322_0370
2010-12-24 17:04:14,420 Stage-1 map = 0%,  reduce = 0%
2010-12-24 17:04:17,443 Stage-1 map = 4%,  reduce = 0%
2010-12-24 17:04:18,459 Stage-1 map = 8%,  reduce = 0%
2010-12-24 17:04:19,468 Stage-1 map = 19%,  reduce = 0%
2010-12-24 17:04:20,478 Stage-1 map = 27%,  reduce = 0%
2010-12-24 17:04:21,486 Stage-1 map = 35%,  reduce = 0%
2010-12-24 17:04:22,546 Stage-1 map = 42%,  reduce = 0%
2010-12-24 17:04:23,697 Stage-1 map = 50%,  reduce = 0%
2010-12-24 17:04:24,714 Stage-1 map = 58%,  reduce = 0%
2010-12-24 17:04:25,724 Stage-1 map = 65%,  reduce = 0%
2010-12-24 17:04:26,733 Stage-1 map = 77%,  reduce = 0%
2010-12-24 17:04:27,792 Stage-1 map = 81%,  reduce = 12%
2010-12-24 17:04:28,800 Stage-1 map = 88%,  reduce = 12%
2010-12-24 17:04:29,813 Stage-1 map = 100%,  reduce = 12%
2010-12-24 17:04:36,866 Stage-1 map = 100%,  reduce = 100%
Ended Job = job_201011022322_0370
OK
1       ed      1
1       ed      1
Time taken: 30.594 seconds
{noformat}

This looks good now. I do not know when exactly.

> Output invalid when choose all columns from left table of a join 
> -----------------------------------------------------------------
>
>                 Key: HIVE-22
>                 URL: https://issues.apache.org/jira/browse/HIVE-22
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Joey Pan
>
> Here is what I observed, in a hive command:  from ad_stat2 join ad  
> on(ad_stat2.ad_id=ad.ad_id) select ad_stat2.*,  ad.ad_id where 
> ad_stat2.ad_clk>1000;
> In the command, 2 tables are involved, the observation is if the output 
> includes all columns of left table(ad_stat2.*), then no matter what columns 
> you pick for the right table, it will print out all columns of right table.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to