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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.5
• Component/s: metastore
• Assignee: Unassigned
• Reporter: Udai Kiran Potluri
• Created: 31/Oct/14 01:49
• Updated: 31/Oct/14 01:49

Description

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

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

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:

hsqldb.default_table_type=cached

instead of

hsqldb.default_table_type=memory

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.