Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 11 Dec 2013 11:57:10 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12682405.1386084067574.16982.1386763030213@arcas>
In-Reply-To: <JIRA.12682405.1386084067574@arcas>
References: <JIRA.12682405.1386084067574@arcas>
Subject: [jira] [Updated] (CASSANDRA-6438) Decide if we want to make user
 types keyspace scoped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-6438:
-----------------------------------------

    Reviewer: Aleksey Yeschenko

> Decide if we want to make user types keyspace scoped
> ----------------------------------------------------
>
>                 Key: CASSANDRA-6438
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6438
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 2.1
>
>         Attachments: 6438.txt
>
>
> Currently, user types are declared at the top level. I wonder however if we might not want to make them scoped to a given keyspace. It was not done in the initial patch for simplicity and because I was not sure of the advantages of doing so. However, if we ever want to use user types in system tables, having them scoped by keyspace means we won't have to care about the new type conflicting with another existing type.
> Besides, having user types be part of a keyspace would allow for slightly more fine grained permissions on them. 


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)