[
https://issues.apache.org/jira/browse/AMBARI-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990691#comment-15990691
]
Hudson commented on AMBARI-20901:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7397 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7397/])
AMBARI-20901. Improvement needed for creating ACID tables. (dipayanb)
(dipayan.bhowmick:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bfcc42dcc76aabe9e00c123b92ea9d40d643c713])
* (edit)
contrib/views/hive20/src/main/resources/ui/app/templates/components/edit-table.hbs
* (edit)
contrib/views/hive20/src/main/resources/ui/app/templates/components/create-table.hbs
* (edit)
contrib/views/hive20/src/main/resources/ui/app/components/create-table.js
> 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)
