sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheolsoo Park (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-519) Update the version of hsqldb decadency to 2.0.0
Date Wed, 25 Jul 2012 06:39:33 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cheolsoo Park updated SQOOP-519:
--------------------------------

    Attachment: SQOOP-519-7.patch

The newest patch fixes all unit test cases.

Regarding TextIncrementalImport, what I end up doing is lowering the level of transaction
isolation of Hsqldb from SERIALIZABLE to READ_COMMITTED.

The problem with using SERIALIZABLE is that it makes the test hang. By looking into JVM thread
dump, the test thread hangs at HsqldbJobStorage.java:705. But this is rather strange because
it is happening while a single thread makes a transaction to Hsqldb! Nevertheless, it does
for whatever reason.

I don't see any particular issue by lowering the isolation level to READ_COMMITTED (default
value), but I suppose that this can change Sqoop metastore's behavior if you set up Sqoop
metastore in such a way that multiple users are allowed to access to it simultaneously. Although
I haven't heard of such use cases, please let me know if this worries you.

Thanks!
                
> Update the version of hsqldb decadency to 2.0.0
> -----------------------------------------------
>
>                 Key: SQOOP-519
>                 URL: https://issues.apache.org/jira/browse/SQOOP-519
>             Project: Sqoop
>          Issue Type: Task
>    Affects Versions: 1.4.1-incubating
>            Reporter: Cheolsoo Park
>            Assignee: Cheolsoo Park
>            Priority: Blocker
>             Fix For: 1.4.2
>
>         Attachments: SQOOP-519-2.patch, SQOOP-519-3.patch, SQOOP-519-4.patch, SQOOP-519-6.patch,
SQOOP-519-7.patch, SQOOP-519.patch
>
>
> Hadoop 2.0.0 depends on hsqldb 2.0.0, and this breaks Sqoop when running against hadoop
2.0.0 since we end up with two different versions of hsqldb in classpath.

--
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