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

Naveen Gangam commented on HIVE-23717:
--------------------------------------

tthere are no plans to backport this to older releases. If you are on hive3, 
then I recommend that you set "hive.create.as.acid" and/or 
"hive.create.as.insert.only" to false in your hive-site.xml. Thanks

> In jdbcUrl add config to create External + purge table by default     
> ------------------------------------------------------------------
>
>                 Key: HIVE-23717
>                 URL: https://issues.apache.org/jira/browse/HIVE-23717
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, Metastore
>    Affects Versions: 3.1.0
>            Reporter: Xiaomeng Zhang
>            Assignee: Xiaomeng Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> External + purge tables are more backward compatible with the old managed 
> tables.
> Applications can use a HS2 URL that sets the session level property for 
> default table type to external-purge tables to be true.
>  As part of this we need a notion of a "session level only" config 
> parameter(s).
> Adding a new jdbc config: *hiveCreateAsExternalLegacy*, a hs2 config 
> *hive.create.as.external.legacy*, when set to true, create external purge 
> table by default.
> Adding *MANAGED* keyword. "create managed table" will create table based on 
> hive.create.as.acid and hive.craete.as.insert.only values, not impacted by 
> the new config.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to