You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vineet Garg (JIRA)" <ji...@apache.org> on 2018/02/04 02:02:00 UTC
[jira] [Updated] (HIVE-18598) Disallow NOT NULL constraints to be
ENABLED/ENFORCED with EXTERNAL table
[ https://issues.apache.org/jira/browse/HIVE-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vineet Garg updated HIVE-18598:
-------------------------------
Description:
HIVE-16605 is enabling/enforcing NOT NULL constraint. But since Hive do not manage the data for external tables and can not enforce constraints it doesn't make sense to allow NOT NULL constraints to be enabled/enforced on external table.
User can still specify RELY to signal optimizer for constraint related optimizations.
was:
Since Hive do not manage the data for external tables and can not enforce constraints it doesn't make sense to allow constraints like PRIMARY KEY, NOT NULL etc for such tables.
User can still specify RELY to signal optimizer for constraint related optimizations.
Summary: Disallow NOT NULL constraints to be ENABLED/ENFORCED with EXTERNAL table (was: Disallow constraints with EXTERNAL table)
> Disallow NOT NULL constraints to be ENABLED/ENFORCED with EXTERNAL table
> ------------------------------------------------------------------------
>
> Key: HIVE-18598
> URL: https://issues.apache.org/jira/browse/HIVE-18598
> Project: Hive
> Issue Type: Task
> Components: SQL
> Reporter: Vineet Garg
> Assignee: Vineet Garg
> Priority: Major
> Attachments: HIVE-18598.1.patch
>
>
> HIVE-16605 is enabling/enforcing NOT NULL constraint. But since Hive do not manage the data for external tables and can not enforce constraints it doesn't make sense to allow NOT NULL constraints to be enabled/enforced on external table.
> User can still specify RELY to signal optimizer for constraint related optimizations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)