[SQOOP-571] Revert SQOOP-519 and SQOOP-524

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.4.2
• Assignee: Cheolsoo Park
• Reporter: Cheolsoo Park
• Created: 12/Aug/12 21:44
• Updated: 14/Aug/12 21:14
• Resolved: 14/Aug/12 10:28

Description

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.

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

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.