[ 
https://issues.apache.org/jira/browse/HIVE-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256985#comment-15256985
 ] 

Hari Sankar Sivarama Subramaniyan commented on HIVE-13290:
----------------------------------------------------------

The only failure that happened locally and was fixed while testing locally :
{code}
Failed tests:
  TestHiveDecimalParse.testDecimalType7:107 FAILED: ParseException line 1:32 
missing ) at ',' near ',' in column name or primary key or foreign key
line 1:33 cannot recognize input near '4' ')' ')' in column name or primary key 
or foreign key

Tests run: 3404, Failures: 1, Errors: 0, Skipped: 2
{code}
 
I have attached test-results.

Thanks
Hari

> Support primary keys/foreign keys constraint as part of create table command 
> in Hive
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-13290
>                 URL: https://issues.apache.org/jira/browse/HIVE-13290
>             Project: Hive
>          Issue Type: Sub-task
>          Components: CBO, Logical Optimizer
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>         Attachments: HIVE-13290.1.patch, HIVE-13290.2.patch, 
> HIVE-13290.3.patch, HIVE-13290.4.patch, HIVE-13290.5.patch, 
> HIVE-13290.6.patch, HIVE-13290.7.patch, HIVE-13290.8.patch
>
>
> SUPPORT for the following statements
> {code}
> CREATE TABLE product 
>   ( 
>      product_id        INTEGER, 
>      product_vendor_id INTEGER, 
>      PRIMARY KEY (product_id)  DISABLE NOVALIDATE, 
>      CONSTRAINT product_fk_1 FOREIGN KEY (product_vendor_id) REFERENCES 
> vendor(vendor_id)  DISABLE NOVALIDATE
>   ); 
> CREATE TABLE vendor 
>   ( 
>      vendor_id INTEGER, 
>      PRIMARY KEY (vendor_id)  DISABLE NOVALIDATE RELY
>   ); 
> {code}
> In the above syntax, [CONSTRAINT constraint-Name] is optional. If this is not 
> specified by the user, we will use system generated constraint name. For the 
> purpose of simplicity, we will allow  CONSTRAINT option for foreign keys and 
> not primary key since there is only one primary key per table. The 
> RELY/NORELY keyword is also optional.



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

Reply via email to