<?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 incremental import using composite primary key as merge-key in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114517#M77313</link>
    <description>&lt;P&gt;Currently sqoop incremental does not support composite primary key as per the design,but an alternative would be to concatenate the composite primary key 
concat(PK1,PK2) as UniqueId while importing and using the &lt;STRONG&gt;UniqueId &lt;/STRONG&gt;as --merger-key instead of a single primary key.&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jan 2017 13:05:09 GMT</pubDate>
    <dc:creator>klksrinivas</dc:creator>
    <dc:date>2017-01-06T13:05:09Z</dc:date>
    <item>
      <title>sqoop incremental import using composite primary key as merge-key</title>
      <link>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114516#M77312</link>
      <description>&lt;P&gt;sqoop incremental import using composite primary key as merge-key&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jan 2017 18:04:09 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114516#M77312</guid>
      <dc:creator>klksrinivas</dc:creator>
      <dc:date>2017-01-05T18:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: sqoop incremental import using composite primary key as merge-key</title>
      <link>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114517#M77313</link>
      <description>&lt;P&gt;Currently sqoop incremental does not support composite primary key as per the design,but an alternative would be to concatenate the composite primary key 
concat(PK1,PK2) as UniqueId while importing and using the &lt;STRONG&gt;UniqueId &lt;/STRONG&gt;as --merger-key instead of a single primary key.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2017 13:05:09 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114517#M77313</guid>
      <dc:creator>klksrinivas</dc:creator>
      <dc:date>2017-01-06T13:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: sqoop incremental import using composite primary key as merge-key</title>
      <link>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114518#M77314</link>
      <description>&lt;P&gt;Hi @&lt;A rel="user" href="https://community.cloudera.com/users/2508/klksrinivas.html" nodeid="2508"&gt;Krishna Srinivas&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I am facing the same issue, where in I have to specify the composite primary key in merge-key. But it is giving me the error. Can you please explain me on how can I achieve the above mentioned answer by taking an example. That will help me understand more clearly.&lt;/P&gt;&lt;P&gt;Thanks in Advance !!&lt;/P&gt;</description>
      <pubDate>Thu, 21 Dec 2017 03:58:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/sqoop-incremental-import-using-composite-primary-key-as/m-p/114518#M77314</guid>
      <dc:creator>jyothireddy119</dc:creator>
      <dc:date>2017-12-21T03:58:06Z</dc:date>
    </item>
  </channel>
</rss>

