[
https://issues.apache.org/jira/browse/CASSANDRA-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-6438:
----------------------------------------
Attachment: 6438.txt
Attaching patch for this. I'll note that because type are now dependant on the
keyspace, we now have to parse types into "unprepared types" that needs to be
prepared by providing the currently logged keyspace later on. And because of
type-casts, this means we now have to pass the current keyspace to quite a
bunch of methods. Not a big deal, those are trivial changes, but that's why the
patch impact so many files that don't seem initially related.
> 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
> 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#6144)
