[
https://issues.apache.org/jira/browse/CASSANDRA-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056418#comment-14056418
]
Tyler Hobbs commented on CASSANDRA-7395:
----------------------------------------
bq. Having function definitions not be extraneous to CQL also mean that we can
enforce some security rules (that is to have per-user rights to
define/update/remove functions). This also makes it clear when say
notifications should be sent for newly added functions, etc...
Excellent points.
bq. Regarding bundle/namespaces, I agree it's good to have some and I'm not
sure what would be the best way to make them fit with what's above.
I like Robert's suggestion to use {{::}} as a namespace delimiter and use "" as
the namespace if absent. That's pretty lightweight and familiar syntax.
bq. What I would do here is start with that AS foo.bar.Class.method support.
+1
Regarding functional indexes and deterministic functions, postgres and Oracle
both require indexed functions to be declared as deterministic, so it would be
reasonable to adopt that in Cassandra.
> Support for pure user-defined functions (UDF)
> ---------------------------------------------
>
> Key: CASSANDRA-7395
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7395
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Labels: cql
> Fix For: 3.0
>
> Attachments: 7395-v2.diff, 7395.diff
>
>
> We have some tickets for various aspects of UDF (CASSANDRA-4914,
> CASSANDRA-5970, CASSANDRA-4998) but they all suffer from various degrees of
> ocean-boiling.
> Let's start with something simple: allowing pure user-defined functions in
> the SELECT clause of a CQL query. That's it.
> By "pure" I mean, must depend only on the input parameters. No side effects.
> No exposure to C* internals. Column values in, result out.
> http://en.wikipedia.org/wiki/Pure_function
--
This message was sent by Atlassian JIRA
(v6.2#6252)
