hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2084) Upgrade datanucleus from 2.0.3 to 3.0.1
Date Wed, 04 Apr 2012 21:47:19 GMT

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

Sushanth Sowmyan commented on HIVE-2084:
----------------------------------------

Hi Namit,

I've run a fair number of iterations of tests against the DN versions, and I find that the
test that you posted up on that jira still fails a few times with DataNucleus 3.0.8 about
0.5% of the time saying that the table was not found. With DN 2.0.3, I have no failures.

However, if I increase the parallelism, from 5 concurrent runs, to, say, about 20, all 3 versions
of DN wind up showing those kinds of 'table not found' error, and quite often (10-20% of the
time) and occur even with simpler statements like 'describe table' and 'show partitions extended'.
I think we may have a case of timeouts that are being incorrectly reported.
                
> Upgrade datanucleus from 2.0.3 to 3.0.1
> ---------------------------------------
>
>                 Key: HIVE-2084
>                 URL: https://issues.apache.org/jira/browse/HIVE-2084
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Ning Zhang
>            Assignee: Sushanth Sowmyan
>              Labels: datanucleus
>         Attachments: HIVE-2084.1.patch.txt, HIVE-2084.2.patch.txt, HIVE-2084.D2397.1.patch,
HIVE-2084.patch
>
>
> It seems the datanucleus 2.2.3 does a better join in caching. The time it takes to get
the same set of partition objects takes about 1/4 of the time it took for the first time.
While with 2.0.3, it took almost the same amount of time in the second execution. We should
retest the test case mentioned in HIVE-1853, HIVE-1862.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message