[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-21 Thread Hive QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204455#comment-15204455
 ] 

Hive QA commented on HIVE-13298:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12794283/HIVE-13298.01.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 9832 tests executed
*Failed tests:*
{noformat}
TestSparkCliDriver-groupby3_map.q-sample2.q-auto_join14.q-and-12-more - did not 
produce a TEST-*.xml file
TestSparkCliDriver-groupby_map_ppr_multi_distinct.q-table_access_keys_stats.q-groupby4_noskew.q-and-12-more
 - did not produce a TEST-*.xml file
TestSparkCliDriver-join_rc.q-insert1.q-vectorized_rcfile_columnar.q-and-12-more 
- did not produce a TEST-*.xml file
TestSparkCliDriver-ppd_join4.q-join9.q-ppd_join3.q-and-12-more - did not 
produce a TEST-*.xml file
TestSparkCliDriver-timestamp_lazy.q-bucketsortoptimize_insert_4.q-date_udf.q-and-12-more
 - did not produce a TEST-*.xml file
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/7329/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/7329/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-7329/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 5 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12794283 - PreCommit-HIVE-TRUNK-Build

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.01.patch, HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-19 Thread Sergey Shelukhin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202315#comment-15202315
 ] 

Sergey Shelukhin commented on HIVE-13298:
-

[~ashutoshc] ping?

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.01.patch, HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-19 Thread Sergey Shelukhin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201815#comment-15201815
 ] 

Sergey Shelukhin commented on HIVE-13298:
-

I guess that's another consideration. In that case we also cannot switch. My 
original question is misguided, it doesn't actually matter which side of an 
inner join is which. But if we want to preserve column order, I'd have to 
remove the switch logic and just keep the error.

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-19 Thread Ashutosh Chauhan (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202415#comment-15202415
 ] 

Ashutosh Chauhan commented on HIVE-13298:
-

+1

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.01.patch, HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-18 Thread Sergey Shelukhin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200125#comment-15200125
 ] 

Sergey Shelukhin commented on HIVE-13298:
-

[~jcamachorodriguez] fyi also. Do you know about the join semantics (the above 
comment)? Is some change needed for CBO?

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-18 Thread Hive QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202414#comment-15202414
 ] 

Hive QA commented on HIVE-13298:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12793906/HIVE-13298.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 8 failed/errored test(s), 9821 tests executed
*Failed tests:*
{noformat}
TestSparkCliDriver-groupby3_map.q-sample2.q-auto_join14.q-and-12-more - did not 
produce a TEST-*.xml file
TestSparkCliDriver-groupby_map_ppr_multi_distinct.q-table_access_keys_stats.q-groupby4_noskew.q-and-12-more
 - did not produce a TEST-*.xml file
TestSparkCliDriver-join_rc.q-insert1.q-vectorized_rcfile_columnar.q-and-12-more 
- did not produce a TEST-*.xml file
TestSparkCliDriver-ppd_join4.q-join9.q-ppd_join3.q-and-12-more - did not 
produce a TEST-*.xml file
TestSparkCliDriver-timestamp_lazy.q-bucketsortoptimize_insert_4.q-date_udf.q-and-12-more
 - did not produce a TEST-*.xml file
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_auto_sortmerge_join_8
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver_tez_join_hash
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver_tez_join_hash
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/7307/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/7307/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-7307/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 8 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12793906 - PreCommit-HIVE-TRUNK-Build

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.01.patch, HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HIVE-13298) nested join support causes undecipherable errors in SemanticAnalyzer

2016-03-18 Thread Jesus Camacho Rodriguez (JIRA) 

[ 
https://issues.apache.org/jira/browse/HIVE-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201381#comment-15201381
 ] 

Jesus Camacho Rodriguez commented on HIVE-13298:


[~sershe], thanks for pinging me. I do not know if I got properly the problem 
you are facing; is it the order of the columns for full outer join? Or for 
every kind of join? Got confused with the inner join semantics comment...

I think SQL standard specifies that column order for * should be the order of 
the columns in the table. For the query given, we create a cartesian product of 
tables {{a,b}}, and then we filter them. Thus, I would assume it is correct to 
set the order of columns to: _columns of a + columns of b_ in that case. Did 
you mean that by "switching the join sides"?

> nested join support causes undecipherable errors in SemanticAnalyzer
> 
>
> Key: HIVE-13298
> URL: https://issues.apache.org/jira/browse/HIVE-13298
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13298.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)