[
https://issues.apache.org/jira/browse/AMBARI-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990692#comment-15990692
]
Hadoop QA commented on AMBARI-20901:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12865721/AMBARI-20901.branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11555//console
This message is automatically generated.
> Improvement needed for creating ACID tables
> -------------------------------------------
>
> Key: AMBARI-20901
> URL: https://issues.apache.org/jira/browse/AMBARI-20901
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.5.0
> Reporter: DIPAYAN BHOWMICK
> Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.1
>
> Attachments: AMBARI-20901.branch-2.5.patch
>
>
> Right now you need to mark a column as clustered before you try to mark the
> table as transactional.
> If you don't it doesn't prompt for number of buckets (which is mandatory).
> Then the create will fail for reasons that are not in the exception / error.
> Ideal would be if the user could choose the clustering columns when they mark
> the table as transactional. Clustering is required for transactional but
> transactional is not required for clustering. Right now the decoupling is
> confusing. We should consider this one-way linkage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
