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

Hive QA commented on HIVE-16867:
--------------------------------



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

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/5614/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/5614/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-5614/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hiveptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ date '+%Y-%m-%d %T.%3N'
2017-06-10 03:19:32.700
+ [[ -n /usr/lib/jvm/java-8-openjdk-amd64 ]]
+ export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+ export 
PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ 
PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'MAVEN_OPTS=-Xmx1g '
+ MAVEN_OPTS='-Xmx1g '
+ cd /data/hiveptest/working/
+ tee /data/hiveptest/logs/PreCommit-HIVE-Build-5614/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ date '+%Y-%m-%d %T.%3N'
2017-06-10 03:19:32.702
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at ca8ba1d HIVE-16837: MetadataOnly optimizer conflicts with count 
distinct rewrite (Pengcheng Xiong, reviewed by Ashutosh Chauhan)
+ git clean -f -d
+ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
+ git reset --hard origin/master
HEAD is now at ca8ba1d HIVE-16837: MetadataOnly optimizer conflicts with count 
distinct rewrite (Pengcheng Xiong, reviewed by Ashutosh Chauhan)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2017-06-10 03:19:36.996
+ patchCommandPath=/data/hiveptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hiveptest/working/scratch/build.patch
+ [[ -f /data/hiveptest/working/scratch/build.patch ]]
+ chmod +x /data/hiveptest/working/scratch/smart-apply-patch.sh
+ /data/hiveptest/working/scratch/smart-apply-patch.sh 
/data/hiveptest/working/scratch/build.patch
error: patch failed: ql/src/test/results/clientpositive/perf/query78.q.out:133
error: ql/src/test/results/clientpositive/perf/query78.q.out: patch does not 
apply
The patch does not appear to apply with p0, p1, or p2
+ exit 1
'
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12872391 - PreCommit-HIVE-Build

> Extend shared scan optimizer to reuse computation from other operators
> ----------------------------------------------------------------------
>
>                 Key: HIVE-16867
>                 URL: https://issues.apache.org/jira/browse/HIVE-16867
>             Project: Hive
>          Issue Type: Improvement
>          Components: Physical Optimizer
>    Affects Versions: 3.0.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-16867.01.patch, HIVE-16867.02.patch, 
> HIVE-16867.patch
>
>
> Follow-up of the work in HIVE-16602.
> HIVE-16602 introduced an optimization that identifies scans on input tables 
> that can be merged so the data is read only once.
> This extension to that rule allows to reuse the computation that is done in 
> the work containing those scans. In particular, we traverse both parts of the 
> plan upstream and reuse the operators if possible.
> Currently, the optimizer will not go beyond the output edge(s) of that work. 
> Follow-up extensions might remove this limitation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to