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

Hive QA commented on HIVE-19995:
--------------------------------



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

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

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12929600/HIVE-19995.02.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12929600 - PreCommit-HIVE-Build

> Aggregate row traffic for acid tables
> -------------------------------------
>
>                 Key: HIVE-19995
>                 URL: https://issues.apache.org/jira/browse/HIVE-19995
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Statistics, Transactions
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: HIVE-19995.01.patch, HIVE-19995.01wip01.patch, 
> HIVE-19995.01wip01.patch, HIVE-19995.01wip02.patch, HIVE-19995.02.patch, 
> HIVE-19995.02.patch
>
>
> for transactional tables we store basic stats in case of explicit 
> analyze/rewrite; but doesn't do anything in other cases....which may even 
> lead to plans which oom...
> It would be better to aggregate the total row traffic...because that is 
> already available; so that operator tree estimations could work with a real 
> upper bound of the row numbers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to