hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-19753) Strict managed tables mode in Hive
Date Sun, 17 Jun 2018 05:28:00 GMT


Hive QA commented on HIVE-19753:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12927899 - PreCommit-HIVE-Build

> Strict managed tables mode in Hive
> ----------------------------------
>                 Key: HIVE-19753
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>            Priority: Major
>         Attachments: HIVE-19753.1.patch, HIVE-19753.2.patch, HIVE-19753.3.patch, HIVE-19753.4.patch
> Create a mode in Hive which enforces that all managed tables are transactional (both
full or insert-only tables allowed). Non-transactional tables, as well as non-native tables,
must be created as external tables when this mode is enabled.
> The idea would be that in strict managed tables mode all of the data written to managed
tables would have been done through Hive.
> The mode would be enabled using config setting hive.strict.managed.tables.

This message was sent by Atlassian JIRA

View raw message