hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-15056) Support index shifting for struct fields
Date Wed, 26 Oct 2016 20:58:59 GMT


Hive QA commented on HIVE-15056:

Here are the results of testing the latest attachment:

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

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 10622 tests executed
*Failed tests:*
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJarWithoutAddDriverClazz[0] (batchId=164)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[0] (batchId=164)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[1] (batchId=164)

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.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 3 tests failed

This message is automatically generated.

ATTACHMENT ID: 12835390 - PreCommit-HIVE-Build

> Support index shifting for struct fields
> ----------------------------------------
>                 Key: HIVE-15056
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: File Formats, Physical Optimizer, Serializers/Deserializers
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>         Attachments: HIVE-15056.1.patch, HIVE-15056.2.patch
> In HIVE-13873, the following case doesn't work:
> {code}
> select s.c from tbl
> {code}
> where {{tbl}} is of schema:
> {code}
> a                   	int
> s                   	struct<b:int,c:string>
> {code}
> This is because currently we generate a "pruned" schema (in terms of {{GroupType}}) for
Parquet reader to scan the data. However, on the Hive side the object inspector still uses
the original schema. In particular, in this case for {{s.c}} the data returned by Parquet
reader is in index 0, but the object inspector tries to read it in index 1. Therefore, in
correct result will be returned.

This message was sent by Atlassian JIRA

View raw message