You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zoltan Haindrich (JIRA)" <ji...@apache.org> on 2018/07/01 10:46:00 UTC
[jira] [Updated] (HIVE-19995) Aggregate row traffic for acid tables
[ https://issues.apache.org/jira/browse/HIVE-19995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltan Haindrich updated HIVE-19995:
------------------------------------
Attachment: HIVE-19995.03.patch
> 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, 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)