hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19995) Aggregate row traffic for acid tables
Date Tue, 03 Jul 2018 09:00:00 GMT

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

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

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m 16s{color} | {color:red}
/data/hiveptest/logs/PreCommit-HIVE-Build-12343/patches/PreCommit-HIVE-Build-12343.patch does
not apply to master. Rebase required? Wrong Branch? See http://cwiki.apache.org/confluence/display/Hive/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Console output | http://104.198.109.242/logs//PreCommit-HIVE-Build-12343/yetus.txt |
| Powered by | Apache Yetus    http://yetus.apache.org |


This message was automatically generated.



> 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
>             Fix For: 4.0.0
>
>         Attachments: HIVE-19995.01-branch-3.patch, HIVE-19995.01.patch, HIVE-19995.01wip01.patch,
HIVE-19995.01wip01.patch, HIVE-19995.01wip02.patch, HIVE-19995.02.patch, HIVE-19995.02.patch,
HIVE-19995.03.patch, HIVE-19995.03.patch, HIVE-19995.03.patch, HIVE-19995.03.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)

Mime
View raw message