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

Hive QA commented on HIVE-8290:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12671955/HIVE-8290.2.patch

{color:green}SUCCESS:{color} +1 6380 tests passed

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1054/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1054/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1054/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12671955

> 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)

Reply via email to