[
https://issues.apache.org/jira/browse/HIVE-10902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570416#comment-14570416
]
Damien Carol commented on HIVE-10902:
-------------------------------------
Tested on master with and without data. It works.
{code:sql}
create table t1(id string);
create table t2(id string);
select t1.INPUT__FILE__NAME
from t1 join t2 on t1.id = t2.id;
{code}
With data :
{code:sql}
insert into t1 values("test1");
insert into t2 values("test1");
{code}
{noformat}
0: jdbc:hive2://nc-h07:10000/> select t1.INPUT__FILE__NAME
0: jdbc:hive2://nc-h07:10000/> from t1 join t2 on t1.id = t2.id;
INFO : Session is already open
INFO :
INFO : Status: Running (Executing on YARN cluster with App id
application_1433166587850_0006)
INFO : Map 1: -/- Map 2: -/-
INFO : Map 1: 0/1 Map 2: 0/1
INFO : Map 1: 0/1 Map 2: 0(+1)/1
INFO : Map 1: 0/1 Map 2: 1/1
INFO : Map 1: 0(+1)/1 Map 2: 1/1
INFO : Map 1: 1/1 Map 2: 1/1
+----------------------------------------------------------+--+
| t1.input__file__name |
+----------------------------------------------------------+--+
| hdfs://nc-h07/user/hive/warehouse/damien.db/t1/000000_0 |
+----------------------------------------------------------+--+
1 row selected (1.588 seconds)
{noformat}
> hive fails on virtual columns when using any joins
> --------------------------------------------------
>
> Key: HIVE-10902
> URL: https://issues.apache.org/jira/browse/HIVE-10902
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.14.0
> Environment: cloudera 5.3.3, but happening also in hdp 2.2 and also
> on clean installs on linux.
> Reporter: Rani Yaroshinsky
>
> did the following:
> {code:sql}
> create table t1(id string);
> create table t2(id string);
> select t1.INPUT__FILE__NAME
> from t1 join t2 on t1.id = t2.id;
> {code}
> {noformat}
> fails on: Execution failed with exit status: 2
> {noformat}
> notice this happens also on self joins:select t1_1.INPUT__FILE__NAME from t1
> t1_1 join t1 t1_2 on t1_1.id = t1_2.id
> [HIVE-8186] is related to self joins and said the issue has been resolved,
> but this does not seem to be the case.
> thanks for your help.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
