[
https://issues.apache.org/jira/browse/HIVE-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583123#comment-16583123
]
Alexander Kolbasov commented on HIVE-18294:
-------------------------------------------
[~ekoifman] [~alangates] In {{TransactionalValidationListener.makeAcid()}}
there is the following code:
{code}
if(!TableType.MANAGED_TABLE.toString().equalsIgnoreCase(newTable.getTableType()))
{
//todo should this check be in conformToAcid()?
LOG.info("Could not make " + Warehouse.getQualifiedName(newTable) + "
acid: it's " +
newTable.getTableType());
return;
}
{code}
What is the expected behavior for tables that have MANAGED_TABLE type but have
EXTERNAL parameter set? Should these be excluded as well?
> add switch to make acid table the default
> -----------------------------------------
>
> Key: HIVE-18294
> URL: https://issues.apache.org/jira/browse/HIVE-18294
> Project: Hive
> Issue Type: Sub-task
> Components: Transactions
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18294.01.patch, HIVE-18294.03.patch,
> HIVE-18294.04.patch, HIVE-18294.05.patch
>
>
> it would be convenient for testing to have a switch that enables the behavior
> where all suitable table tables (currently ORC + not sorted) are
> automatically created with transactional=true, ie. full acid.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
