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

Cheolsoo Park commented on SQOOP-508:
-------------------------------------

Reviwd board:
https://reviews.apache.org/r/5548/
                
> Sqoop metastore cannot be started due to missing hsqldb jar file
> ----------------------------------------------------------------
>
>                 Key: SQOOP-508
>                 URL: https://issues.apache.org/jira/browse/SQOOP-508
>             Project: Sqoop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.4.1-incubating
>            Reporter: Cheolsoo Park
>            Assignee: Cheolsoo Park
>            Priority: Critical
>             Fix For: 1.4.2
>
>
> This is a packing issue. Since a hsqldb jar is not packed in the distribution 
> tarball, sqoop-metastore fails with the following error:
> {code}
> 12/06/25 01:15:46 WARN hsqldb.HsqldbMetaStore: The location for metastore 
> data has not been explicitly set. Placing shared metastore files in 
> /home/cheolsoo/.sqoop/shared-metastore.db
> Exception in thread "main" java.lang.NoClassDefFoundError: org/hsqldb/Server
>       at 
> org.apache.sqoop.metastore.hsqldb.HsqldbMetaStore.start(HsqldbMetaStore.java:111)
> {code}
> To reproduce the issue, please do the following:
> 1) checkout sqoop trunk
> 2) ant clean tar
> 3) cd build/sqoop-1.4.2-incubating-SNAPSHOT.bin__hadoop-0.23
> 4) ./bin/sqoop metastore
> This may be not an issue if a hsqldb jar is already installed by another 
> project and therefore exists in classpath. For example, CDH3 installs a 
> hsqldb jar in /usr/lib/hadoop/lib. However, it is not always true in all 
> distributions (e.g. CDH4).
> The fix seems to include a hsqldb jar in the distribution tarball.
> There is also a bigtop jira 
> [BIGTOP-639|https://issues.apache.org/jira/browse/BIGTOP-639] regarding this 
> issue.

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