[
https://issues.apache.org/jira/browse/IMPALA-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981990#comment-16981990
]
ASF subversion and git services commented on IMPALA-9104:
---------------------------------------------------------
Commit 1f792bea4779229acbaaa40d4904df4546658bfb in impala's branch
refs/heads/master from Sahil Takiar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=1f792be ]
IMPALA-9188: Composite primary keys should use same constraint name
After IMPALA-9104, dataload started failing when USE_CDP_HIVE=true
because of HIVE-16603 (Enforce foreign keys to refer to primary keys or
unique keys), which is in Hive 3 but not Hive 2.
This patch fixes a bug from IMPALA-2112 where Impala was generating a
unique constraint name for each column in a composite primary key,
rather than using the same constraint name for each column.
Testing:
* Ran dataload + core tests with USE_CDP_HIVE=[true/false]
Change-Id: I7a91658945b0355753c3cf05be195757b37edaf4
Reviewed-on: http://gerrit.cloudera.org:8080/14792
Reviewed-by: Sahil Takiar <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Add support for retrieval of primary keys and foreign keys in
> impala-hs2-server.
> --------------------------------------------------------------------------------
>
> Key: IMPALA-9104
> URL: https://issues.apache.org/jira/browse/IMPALA-9104
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Anurag Mantripragada
> Assignee: Anurag Mantripragada
> Priority: Critical
>
> Impala's TCLIService.thrift files was taken from Hive-1 days and does not
> contain APIs related to primary keys and foreign keys that was added to Hive
> jdbc driver start Hive-2.1. We need to port these APIs inorder to be able to
> use them in Impala JDBC clients.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
