hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-12995) LLAP: Synthetic file ids need collision checks
Date Tue, 15 Mar 2016 19:53:33 GMT


Hive QA commented on HIVE-12995:

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 4 failed/errored test(s), 9825 tests executed
*Failed tests:*
TestSparkCliDriver-groupby3_map.q-sample2.q-auto_join14.q-and-12-more - did not produce a
TEST-*.xml file
- did not produce a TEST-*.xml file
TestSparkCliDriver-join_rc.q-insert1.q-vectorized_rcfile_columnar.q-and-12-more - did not
produce a TEST-*.xml file
TestSparkCliDriver-ppd_join4.q-join9.q-ppd_join3.q-and-12-more - did not produce a TEST-*.xml

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: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12793362 - PreCommit-HIVE-TRUNK-Build

> LLAP: Synthetic file ids need collision checks
> ----------------------------------------------
>                 Key: HIVE-12995
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>    Affects Versions: 2.1.0
>            Reporter: Gopal V
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-12995.01.patch, HIVE-12995.02.patch, HIVE-12995.03.patch, HIVE-12995.04.patch,
> LLAP synthetic file ids do not have any way of checking whether a collision occurs other
than a data-error.
> Synthetic file-ids have only been used with unit tests so far - but they will be needed
to add cache mechanisms to non-HDFS filesystems.
> In case of Synthetic file-ids, it is recommended that we track the full-tuple (path,
mtime, len) in the cache so that a cache-hit for the synthetic file-id can be compared against
the parameters & only accepted if those match.

This message was sent by Atlassian JIRA

View raw message