hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-11586) ObjectInspectorFactory.getReflectionObjectInspector is not thread-safe
Date Wed, 19 Aug 2015 12:16:45 GMT


Hive QA commented on HIVE-11586:

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

Here are the results of testing the latest attachment:

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

Test results:
Console output:
Test logs:

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.

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

> ObjectInspectorFactory.getReflectionObjectInspector is not thread-safe
> ----------------------------------------------------------------------
>                 Key: HIVE-11586
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>             Fix For: 1.3.0, 2.0.0
>         Attachments: HIVE-11586.1.patch, HIVE-11586.2.patch
> ObjectInspectorFactory#getReflectionObjectInspectorNoCache addes newly create object
inspector to the cache before calling its init() method, to allow reusing the cache when dealing
with recursive types. So a second thread can then call getReflectionObjectInspector and fetch
an uninitialized instance of ReflectionStructObjectInspector.
> Another issue is that if two threads calls ObjectInspectorFactory.getReflectionObjectInspector
at the same time. One thread could get an object inspector not in the cache, i.e. they could
both call getReflectionObjectInspectorNoCache() but only one will put the new object inspector
to cache successfully.

This message was sent by Atlassian JIRA

View raw message