Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sun, 30 Apr 2017 20:26:04 +0000 (UTC)
From: "DIPAYAN BHOWMICK (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13068036.1493583950000.88052.1493583964194@Atlassian.JIRA>
In-Reply-To: <JIRA.13068036.1493583950000@Atlassian.JIRA>
References: <JIRA.13068036.1493583950000@Atlassian.JIRA> <JIRA.13068036.1493583950093@jira-lw-us.apache.org>
Subject: [jira] [Created] (AMBARI-20901) Improvement needed for creating
 ACID tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 30 Apr 2017 20:26:09 -0000

DIPAYAN BHOWMICK created AMBARI-20901:
-----------------------------------------

             Summary: 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


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)