cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9409) Ensure that UDF and UDAs are keyspace-isolated
Date Wed, 20 May 2015 22:03:04 GMT

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

Alan Boudreault updated CASSANDRA-9409:
---------------------------------------
    Assignee: Alan Boudreault  (was: Robert Stupp)

> Ensure that UDF and UDAs are keyspace-isolated
> ----------------------------------------------
>
>                 Key: CASSANDRA-9409
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9409
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Alan Boudreault
>              Labels: qa-resolved
>             Fix For: 2.2.0 rc1
>
>         Attachments: 9409-with-system.txt, 9409.txt
>
>
> In table columns we don't allow to use UDTs from other keyspaces.
> We should also make sure that the following is *not* allowed:
> - UDFs taking UDTs from other keyspaces as arguments or return types
> - UDAs using UDFs from other keyspaces as its subfunctions
> The only exception should be made for {{system}} keyspace. UDAs and UDFs from any keyspace
should be able to reference and reuse those.
> Having no dependencies between keyspaces makes this consistent with the way we treat
UDTs, which is important, but also simplifies auth in multi-tenant environments, and is also
crucial to upcoming 3.X strongly consistent schema work (the ability to treat keyspace as
a unit of change and not having to worry about cross-keyspace dependencies).
> P.S. Should *probably* still allow using other keyspaces UDFs and UDAs in {{SELECT}}
statements. Strict isolation in schema dependencies is what matters to me here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message