<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Sqoop Metastore - Usage, Supported databases, backup in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119591#M22378</link>
    <description>&lt;P&gt;sounds good, thanks. I am looking to store last record info at enterprise level metadata store in DB2. &lt;/P&gt;</description>
    <pubDate>Thu, 10 Mar 2016 00:26:22 GMT</pubDate>
    <dc:creator>learninghuman</dc:creator>
    <dc:date>2016-03-10T00:26:22Z</dc:date>
    <item>
      <title>Sqoop Metastore - Usage, Supported databases, backup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119588#M22375</link>
      <description>&lt;P&gt;1. Its not very clear from the HDP documentation whether Sqoop supports Mysql or any DB other than HSQLDB. Has any one tried using MySQL or Postgres for the sqoop metastore? &lt;/P&gt;&lt;P&gt;2. I think metastore is required only for the sqoop jobs and not required otherwise. Is this correct?&lt;/P&gt;&lt;P&gt;3. If only HSQLDB is supported, what are the backup, DR strategies for the same?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 23:58:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119588#M22375</guid>
      <dc:creator>learninghuman</dc:creator>
      <dc:date>2016-03-09T23:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: Sqoop Metastore - Usage, Supported databases, backup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119589#M22376</link>
      <description>&lt;P&gt;Sqoop metastore on MySQL is not out but there are jiras open. There are tutorials outthere but i was never successful to make it work.&lt;/P&gt;&lt;P&gt;Yes metastore is for metadata about jobs, storing last record procesaed, job name, etc.&lt;/P&gt;&lt;P&gt;There really aren't any backup strategies for hsqldb. It's a file on disk, while some in memory data is not flushed to disk you have potential Dara loss. Maybe putting it on RAID 1? Use ECC memory chips, etc.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 00:05:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119589#M22376</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-03-10T00:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Sqoop Metastore - Usage, Supported databases, backup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119590#M22377</link>
      <description>&lt;P&gt;I should mention that you can store job definition in source control and write out the last record procesaed to an additional destination like hdfs as precaution. I would do that with Java hdfs api at some point to make sure not losing the row sequence.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 00:20:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119590#M22377</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-03-10T00:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: Sqoop Metastore - Usage, Supported databases, backup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119591#M22378</link>
      <description>&lt;P&gt;sounds good, thanks. I am looking to store last record info at enterprise level metadata store in DB2. &lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 00:26:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119591#M22378</guid>
      <dc:creator>learninghuman</dc:creator>
      <dc:date>2016-03-10T00:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: Sqoop Metastore - Usage, Supported databases, backup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119592#M22379</link>
      <description>&lt;P&gt;Sure whatever works, you can show info on completed Sqoop job in metastore and parse that, then store it in whatever means convenient for you.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 00:31:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119592#M22379</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-03-10T00:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: Sqoop Metastore - Usage, Supported databases, backup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119593#M22380</link>
      <description>&lt;P&gt;We are currently using a mysql metastore in our test environment so it is possible (we run hpd 2.5). Only thing is that oozie requires the sqoop-site.xml file to be placed somewhere in hdfs to access the metastore. We don't really like the idea that passwords are just stored like that..&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 19:58:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sqoop-Metastore-Usage-Supported-databases-backup/m-p/119593#M22380</guid>
      <dc:creator>rene_sluiter</dc:creator>
      <dc:date>2016-12-14T19:58:14Z</dc:date>
    </item>
  </channel>
</rss>

