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

Hive QA commented on HIVE-10191:
--------------------------------



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

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

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

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4472/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4472/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-4472/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

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

> ORC: Cleanup writer per-row synchronization
> -------------------------------------------
>
>                 Key: HIVE-10191
>                 URL: https://issues.apache.org/jira/browse/HIVE-10191
>             Project: Hive
>          Issue Type: Bug
>          Components: File Formats
>    Affects Versions: 1.2.0
>            Reporter: Gopal V
>            Assignee: Gopal V
>         Attachments: HIVE-10191.1.patch, HIVE-10191.2.patch, 
> HIVE-10191.3.patch, HIVE-10191.4.patch, HIVE-10191.5.patch
>
>
> ORC writers were originally meant to be thread-safe, but in the present day 
> implementation each ORC writer is entirely share-nothing which converts most 
> of the synchronized blocks in ORC as entirely uncontested locks.
> These uncontested locks prevent the JVM from inlining/optimizing these 
> methods, while adding no extra thread-safety to the ORC writers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to