sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2443) Sqoop2: Generic JDBC: Properly detect compound primary keys in GenericJdbcExecutor
Date Wed, 12 Aug 2015 20:10:46 GMT

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

Jarek Jarcec Cecho updated SQOOP-2443:
--------------------------------------
    Attachment: SQOOP-2443.patch

> Sqoop2: Generic JDBC: Properly detect compound primary keys in GenericJdbcExecutor
> ----------------------------------------------------------------------------------
>
>                 Key: SQOOP-2443
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2443
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.7
>
>         Attachments: SQOOP-2443.patch, SQOOP-2443.patch
>
>
> [GenericJdbcExecutor.getPrimaryKey|https://github.com/apache/sqoop/blob/sqoop2/connector/connector-generic-jdbc/src/test/java/org/apache/sqoop/connector/jdbc/TestToInitializer.java#L195]
currently returns the first column of the primary key. This works well if the table have one
single column as PK, but won't work correctly when the table have compound key. I would like
to return entire PK here and let the user of this method decides what to do (report error
or use one of the columns of the key).



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

Mime
View raw message