You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Cheolsoo Park (JIRA)" <ji...@apache.org> on 2012/08/12 23:44:37 UTC
[jira] [Created] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Cheolsoo Park created SQOOP-571:
-----------------------------------
Summary: 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
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
[jira] [Updated] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheolsoo Park updated SQOOP-571:
--------------------------------
Attachment: SQOOP-571.patch
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434523#comment-13434523 ]
Hudson commented on SQOOP-571:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop23 #140 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop23/140/])
Changelog update for 1.4.2
Add:
* SQOOP-571 Revert SQOOP-519 and SQOOP-524
* SQOOP-574 Create a Hadoop-2.0.0 build profile (Revision 1372831)
SQOOP-571. Revert SQOOP-519 and SQOOP-524.
(Cheolsoo Park via Jarek Jarcec Cecho) (Revision 1372828)
Result = SUCCESS
jarcec :
Files :
* /sqoop/trunk/CHANGELOG.txt
jarcec :
Files :
* /sqoop/trunk/bin/configure-sqoop
* /sqoop/trunk/ivy.xml
* /sqoop/trunk/ivy/libraries.properties
* /sqoop/trunk/ivy/sqoop-test.xml
* /sqoop/trunk/ivy/sqoop.xml
* /sqoop/trunk/src/java/org/apache/sqoop/metastore/hsqldb/HsqldbJobStorage.java
* /sqoop/trunk/src/java/org/apache/sqoop/metastore/hsqldb/HsqldbMetaStore.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestAvroExport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestAvroImport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestExport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestMultiCols.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/hive/TestHiveImport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleCompatTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/mapreduce/db/TestDataDrivenDBInputFormat.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/testutil/ManagerCompatTestCase.java
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432994#comment-13432994 ]
Cheolsoo Park commented on SQOOP-571:
-------------------------------------
Hi Abhijeet,
To answer your questions,
1) True, MAPRECUDE-4498 is not out yet, but it's going to be backported to the next release of CDH4 that is coming pretty soon.
2) Hsqldb-1.8.0 is shipped by MR1. If you look at CDH4.0 for example, you will find it under /usr/lib/hadoop-0.20-mapreduce/lib.
I must admit that the hadoop distro that I am having trouble with is CDH, but these are equally applicable to to any hadoop distro that ships hsqldb-1.8.x in it.
Thanks!
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432851#comment-13432851 ]
Cheolsoo Park commented on SQOOP-571:
-------------------------------------
Review board:
https://reviews.apache.org/r/6559/
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Abhijeet Gaikwad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433053#comment-13433053 ]
Abhijeet Gaikwad commented on SQOOP-571:
----------------------------------------
As Jarcec suggested, if hsqldb-2.x is not in any hadoop's classpath, then SQOOP-519 is an invalid bug - implies SQOOP-524 is invalid.
Cheolsoo - Can you please test this patch for a simple import/export with hadoop 2.x and CDH4 clusters, if you have them already. (If you don't have a cluster let me know - can try and setup a single-node.)
If the tests are a success, I +1 Jarcec's suggestion.
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433140#comment-13433140 ]
Jarek Jarcec Cecho commented on SQOOP-571:
------------------------------------------
Agreed. I'll wait to see Abhijeet's +1.
Jarcec
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434519#comment-13434519 ]
Hudson commented on SQOOP-571:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop20 #10 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop20/10/])
Changelog update for 1.4.2
Add:
* SQOOP-571 Revert SQOOP-519 and SQOOP-524
* SQOOP-574 Create a Hadoop-2.0.0 build profile (Revision 1372831)
SQOOP-571. Revert SQOOP-519 and SQOOP-524.
(Cheolsoo Park via Jarek Jarcec Cecho) (Revision 1372828)
Result = SUCCESS
jarcec :
Files :
* /sqoop/trunk/CHANGELOG.txt
jarcec :
Files :
* /sqoop/trunk/bin/configure-sqoop
* /sqoop/trunk/ivy.xml
* /sqoop/trunk/ivy/libraries.properties
* /sqoop/trunk/ivy/sqoop-test.xml
* /sqoop/trunk/ivy/sqoop.xml
* /sqoop/trunk/src/java/org/apache/sqoop/metastore/hsqldb/HsqldbJobStorage.java
* /sqoop/trunk/src/java/org/apache/sqoop/metastore/hsqldb/HsqldbMetaStore.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestAvroExport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestAvroImport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestExport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestMultiCols.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/hive/TestHiveImport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleCompatTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/mapreduce/db/TestDataDrivenDBInputFormat.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/testutil/ManagerCompatTestCase.java
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432999#comment-13432999 ]
Cheolsoo Park commented on SQOOP-571:
-------------------------------------
To be clear, I am running against CDH4.0 that is already shipping hsqldb-1.8.x. The original reason why I bumped the version of hsqdb to 2.x was because MAPREDUCE-4197 introduced hsqldb-2.x in MR2. But now they reverted their change in MAPREDUCE-4498, so there's no need to update it in sqoop.
I should have thought about backward-incompatibilities in the first place, but I was under impression that Hadoop is moving to hsqldb-2.x all together. But I was terribly wrong.
Does this make more sense?
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433757#comment-13433757 ]
Cheolsoo Park commented on SQOOP-571:
-------------------------------------
Here is what I verified with the hadoop-2.0.0-chd-4.0.1 MR2 cluster.
1) Upstream sqoop does not have a profile for hadoop-2.0.0, and hadoop-0.23.x is not binary-compatible with hadoop-2.0.0. So to get upstream sqoop working with cdh-4.0.1, I had to modify build.xml so that I can compile it against hadoop-2.0.0-alpha. (I am going to open a jira to add a profile for hadoop-2.0.0 unless there is already one.)
2) With my patch (i.e. reverting SQOOP-519 and SQOOP0524), I was able to run import/export jobs successfully.
Thanks!
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433802#comment-13433802 ]
Cheolsoo Park commented on SQOOP-571:
-------------------------------------
Filed SQOOP-574 regarding the 2.0.0 build profile.
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Abhijeet Gaikwad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432986#comment-13432986 ]
Abhijeet Gaikwad commented on SQOOP-571:
----------------------------------------
I have few queries:
1. Are you running this on trunk?
MAPREDUCE-4498 is in trunk and is not yet out, I feel we should not worry about it until the next Hadoop release is out.
2. According to MAPREDUCE-4498, they have removed hsqldb from hadoop classpath, how is it that hsqldb-1.8.0 is getting picked up? - It is neither in hadoop nor in sqoop's classpath - let me know if I am missing anything here.
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Abhijeet Gaikwad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433976#comment-13433976 ]
Abhijeet Gaikwad commented on SQOOP-571:
----------------------------------------
Thanks for the above patch(SQOOP-574) Cheolsoo.
Verified Apache hadoop 2.x releases do not contain any reference of hsqldb-2.x jars.
Cheolsoo's experiments sound convincing.
ant test(20,23,100,200) successful. Will update this on Review board.
+1
Thanks.
> 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
[jira] [Commented] (SQOOP-571) Revert SQOOP-519 and SQOOP-524
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434528#comment-13434528 ]
Hudson commented on SQOOP-571:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop100 #10 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop100/10/])
Changelog update for 1.4.2
Add:
* SQOOP-571 Revert SQOOP-519 and SQOOP-524
* SQOOP-574 Create a Hadoop-2.0.0 build profile (Revision 1372831)
SQOOP-571. Revert SQOOP-519 and SQOOP-524.
(Cheolsoo Park via Jarek Jarcec Cecho) (Revision 1372828)
Result = SUCCESS
jarcec :
Files :
* /sqoop/trunk/CHANGELOG.txt
jarcec :
Files :
* /sqoop/trunk/bin/configure-sqoop
* /sqoop/trunk/ivy.xml
* /sqoop/trunk/ivy/libraries.properties
* /sqoop/trunk/ivy/sqoop-test.xml
* /sqoop/trunk/ivy/sqoop.xml
* /sqoop/trunk/src/java/org/apache/sqoop/metastore/hsqldb/HsqldbJobStorage.java
* /sqoop/trunk/src/java/org/apache/sqoop/metastore/hsqldb/HsqldbMetaStore.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestAvroExport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestAvroImport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestExport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/TestMultiCols.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/hive/TestHiveImport.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleCompatTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/mapreduce/db/TestDataDrivenDBInputFormat.java
* /sqoop/trunk/src/test/com/cloudera/sqoop/testutil/ManagerCompatTestCase.java
> 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