hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5298) AvroSerde performance problem caused by HIVE-3833
Date Wed, 18 Sep 2013 20:33:58 GMT


Hive QA commented on HIVE-5298:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 3126 tests passed

Test results:
Console output:

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

This message is automatically generated.
> AvroSerde performance problem caused by HIVE-3833
> -------------------------------------------------
>                 Key: HIVE-5298
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.11.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>             Fix For: 0.13.0
>         Attachments: HIVE-5298.1.patch, HIVE-5298.patch
> HIVE-3833 fixed the targeted problem and made Hive to use partition-level metadata to
initialize object inspector. In doing that, however, it goes thru every file under the table
to access the partition metadata, which is very inefficient, especially in case of multiple
files per partition. This causes more problem for AvroSerde because AvroSerde initialization
accesses schema, which is located on file system. As a result, before hive can process any
data, it needs to access every file for a table, which can take long enough to cause job failure
because of lack of job progress.
> The improvement can be made so that partition metadata is only access once per partition.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message