[
https://issues.apache.org/jira/browse/SQOOP-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694236#comment-14694236
]
Sqoop QA bot commented on SQOOP-2443:
-------------------------------------
Testing file
[SQOOP-2443.patch|https://issues.apache.org/jira/secure/attachment/12750154/SQOOP-2443.patch]
against branch sqoop2 took 0:18:57.294988.
{color:red}Overall:{color} -1 due to an error(s), see details below:
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:red}ERROR:{color} Some of unit tests failed
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1536/artifact/patch-process/test_unit.txt],
executed 1360 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1536/artifact/patch-process/cobertura_report.txt])
{color:red}ERROR:{color} Some of integration tests failed
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1536/artifact/patch-process/test_integration.txt],
executed 159 tests)
* Test {{org.apache.sqoop.integration.server.VersionTest}}
* Test {{org.apache.sqoop.integration.connector.kafka.FromRDBMSToKafkaTest}}
* Test {{org.apache.sqoop.integration.connector.hive.FromRDBMSToKiteHiveTest}}
* Test {{org.apache.sqoop.integration.connector.kafka.FromHDFSToKafkaTest}}
* Test {{org.apache.sqoop.integration.connector.hdfs.AppendModeTest}}
* Test
{{org.apache.sqoop.integration.connector.jdbc.generic.IncrementalReadTest}}
* Test {{org.apache.sqoop.integration.connector.jdbc.generic.PartitionerTest}}
* Test
{{org.apache.sqoop.integration.connector.jdbc.generic.TableStagedRDBMSTest}}
* Test
{{org.apache.sqoop.integration.connector.jdbc.generic.FromRDBMSToHDFSTest}}
* Test {{integration-tests}}
* Test {{org.apache.sqoop.integration.connector.jdbc.generic.AllTypesTest}}
* Test
{{org.apache.sqoop.integration.connector.jdbc.generic.FromHDFSToRDBMSTest}}
* Test {{org.apache.sqoop.integration.server.ShowJobInOrderTest}}
* Test
{{org.apache.sqoop.integration.server.SubmissionWithDisabledModelObjectsTest}}
* Test {{org.apache.sqoop.integration.connector.kite.FromRDBMSToKiteTest}}
* Test {{org.apache.sqoop.integration.connector.hdfs.OutputDirectoryTest}}
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1536/console].
This message is automatically generated.
> 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)
