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

Jarek Jarcec Cecho commented on SQOOP-571:
------------------------------------------

I've took different view on the issue. I've downloaded all 0.23 based hadoop 
distributions that are officially available at hadoop.apache.org - namely 
0.23.0, 0.23.1, 2.0.0, 2.0.1. Please note they all are marked as "alpha".

0.23.0 and 0.23.1 are shipping hsqldb version 1.8.0.7. Versions 2.0.0 and 2.0.1 
do not contain any hsqldb jars inside, which make sense as MAPREDUCE-4197 was 
about adding jars that are requested by examples but not included.

Considering that:

* hadoop 0.20 and 1.x is shipping hsqldb 1.8
* hadoop 2.x is moving hsqldb out
* other components stayed with 1.8 (oozie is quite important component to us as 
we're having users actively using it)
* we've upgraded to 2.x only because hadoop seemed to be also upgrading

I would personaly incline to revert those two JIRAs. What do you think guys? 
(I'll not +1 this on Review board and commit it until we will have an agreement)
                
> Revert SQOOP-519 and SQOOP-524
> ------------------------------
>
>                 Key: SQOOP-571
>                 URL: https://issues.apache.org/jira/browse/SQOOP-571
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Cheolsoo Park
>            Assignee: Cheolsoo Park
>            Priority: Critical
>             Fix For: 1.4.2
>
>         Attachments: SQOOP-571.patch
>
>
> This is a regression from "SQOOP-519: Update the version of hsqldb decadency 
> to 2.x". Even though we set HADOOP_USER_CLASSPATH_FIRST in sqoop-configure.sh 
> as discussed in SQOOP-524, tasks still pick up Hsqldb-1.8.x that is present 
> in classpath.
> {code}
> 12/08/10 11:54:28 INFO mapred.JobClient: Task Id : 
> attempt_201208101150_0001_m_000000_0, Status : FAILED
> Error: 
> org.hsqldb.DatabaseURL.parseURL(Ljava/lang/String;ZZ)Lorg/hsqldb/persist/HsqlProperties;
> 12/08/10 11:54:32 INFO mapred.JobClient: Task Id : 
> attempt_201208101150_0001_m_000000_1, Status : FAILED
> Error: 
> org.hsqldb.DatabaseURL.parseURL(Ljava/lang/String;ZZ)Lorg/hsqldb/persist/HsqlProperties;
> 12/08/10 11:54:35 INFO mapred.JobClient: Task Id : 
> attempt_201208101150_0001_m_000000_2, Status : FAILED
> Error: 
> org.hsqldb.DatabaseURL.parseURL(Ljava/lang/String;ZZ)Lorg/hsqldb/persist/HsqlProperties;
> 12/08/10 11:54:39 INFO mapred.JobClient: Job complete: job_201208101150_0001
> {code}
> Hadoop 2.0 moved the hsqldb-2.x jar out of Hadoop classpath. (Please see 
> MAPREDUCE-4498 for details.) So we no longer have the hsqldb-2.x jar in 
> Hadoop classpath, and upgrading to hsqldb-2.x is no longer needed at all. So 
> I suggest that we should revert SQOOP-519 and SQOOP-524 to avoid any 
> potential issues due to conflicting hsqldb jars 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

        

Reply via email to