You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Richard (JIRA)" <ji...@apache.org> on 2015/03/26 08:34:53 UTC

[jira] [Updated] (SQOOP-1541) SQOOP2: Schema should allow specifying an (optional) primary key

     [ https://issues.apache.org/jira/browse/SQOOP-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard updated SQOOP-1541:
---------------------------
    Fix Version/s:     (was: 1.99.6)
                   2.0.0

> SQOOP2: Schema should allow specifying an (optional) primary key
> ----------------------------------------------------------------
>
>                 Key: SQOOP-1541
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1541
>             Project: Sqoop
>          Issue Type: Improvement
>            Reporter: Gwen Shapira
>             Fix For: 2.0.0
>
>
> TO connector possibly has information about primary keys for the data we are ingesting. If we will preserve it in the Schema, than this will be accessible to the FROM connector. This will allow things like converting a relational schema to a meaningful key-value schema and makes loading data to SEQ files, HBase, Cassandra, etc easier.



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