[
https://issues.apache.org/jira/browse/HIVE-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153473#comment-14153473
]
Alan Gates commented on HIVE-8290:
----------------------------------
bq. This is minor, but would it make sense to move the constant to
AcidInputFormat or some other more directly ACID related class?
I didn't see a general place to put table parameter keys. According to the
Hive jedi master (Ashutosh), there is no central place for them. I agree it
makes sense to collect ACID related ones into one place. In addition to
ACID_TABLE_PROPERTY there's NO_AUTO_COMPACT in Initiator. I'll file a separate
ticket to collect those together, and then the patch to do that will be trivial.
> With DbTxnManager configured, all ORC tables forced to be transactional
> -----------------------------------------------------------------------
>
> Key: HIVE-8290
> URL: https://issues.apache.org/jira/browse/HIVE-8290
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 0.14.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Blocker
> Fix For: 0.14.0
>
> Attachments: HIVE-8290.2.patch, HIVE-8290.patch
>
>
> Currently, once a user configures DbTxnManager to the be transaction manager,
> all tables that use ORC are expected to be transactional. This means they
> all have to have buckets. This most likely won't be what users want.
> We need to add a specific mark to a table so that users can indicate it
> should be treated in a transactional way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
