[jira] [Created] (SQOOP-1648) HSQLDB creates tables in memory even when sqoop-site.xml is set to store to disk

["Udai Kiran Potluri (JIRA)" <ji...@apache.org>]

Udai Kiran Potluri created SQOOP-1648:
-----------------------------------------

             Summary: HSQLDB creates tables in memory even when sqoop-site.xml is set to store to disk
                 Key: SQOOP-1648
                 URL: https://issues.apache.org/jira/browse/SQOOP-1648
             Project: Sqoop
          Issue Type: Bug
          Components: metastore
    Affects Versions: 1.4.5
            Reporter: Udai Kiran Potluri


If the sqoop-site.xml has the following XML snippet:

{code}
<property>
    <name>sqoop.metastore.server.location</name>
    <value>/tmp/sqoop-metastore/shared.db</value>
    <description>Path to the shared metastore database files.
    If this is not set, it will be placed in ~/.sqoop/.
    </description>
  </property>

  <property>
    <name>sqoop.metastore.server.port</name>
    <value>16000</value>
    <description>Port that this metastore should listen on.
    </description>
  </property>
{code}

The database file is not generated. Instead it is stored in memory. That is because the properties file says that hsqldb.default_table_type=memory instead of cached.

To be able to make this store to a file, the following steps are needed:

1. kill the sqoop-metastore process.
2. update the shared.db.properties as below:
{code}
hsqldb.default_table_type=cached
{code}

instead of 

{code}
hsqldb.default_table_type=memory
{code}

3. Start sqoop-metastore again on the HSQLDB server.

This bug does not allow for users to persist their jobs to the database for future use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)