[ 
https://issues.apache.org/jira/browse/HIVE-20338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594493#comment-16594493
 ] 

Hive QA commented on HIVE-20338:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12937347/HIVE-20338.1.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

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

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/13497/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13497/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13497/

Messages:
{noformat}
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
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12937347 - PreCommit-HIVE-Build

> LLAP: Force synthetic file-id for filesystems which have HDFS protocol impls 
> with POSIX mutation semantics
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-20338
>                 URL: https://issues.apache.org/jira/browse/HIVE-20338
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gopal V
>            Assignee: Gopal V
>            Priority: Major
>         Attachments: HIVE-20338.1.patch, HIVE-20338.WIP.patch, 
> HIVE-20338.patch
>
>
> HDFS client protocol is not a guarantee of the immutability of files - the 
> synthetic file-id includes the mtime of the file as well, which is a 
> fail-safe for filesystems which implement the client wire protocol without 
> offering the same storage side restrictions on immutability (i.e allow NFS 
> read-write-modify on the backend).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to