hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-19995) Aggregate row traffic for acid tables
Date Sun, 01 Jul 2018 12:29:00 GMT


Hive QA commented on HIVE-19995:

Here are the results of testing the latest attachment:

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

{color:green}SUCCESS:{color} +1 due to 14639 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12929858 - PreCommit-HIVE-Build

> Aggregate row traffic for acid tables
> -------------------------------------
>                 Key: HIVE-19995
>                 URL:
>             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

View raw message