[
https://issues.apache.org/jira/browse/CASSANDRA-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056371#comment-14056371
]
Robert Stupp commented on CASSANDRA-7395:
-----------------------------------------
bq. Anyway, others may have diverging opinions and I don't feel extremely
strongly about that, just saying that I'm not a fan of adding too much syntax
for it.
Consensus:
{noformat}
CREATE FUNCTION bigint math_sum(a bigint, b bigint) {
return a + b;
};
{noformat}
would create a UDF in the bundle named "" so a {{SELECT math_sum(col_a, col_b)
FROM foo}} would work as well as {{SELECT math::sum(col_a, col_b) FROM foo}} if
there is a UDF bundle "math". Not sure, whether the "" bundle handling bites
named bundles - but it should not. So users have the option to do it the one or
the other way - use unbundled UDFs for simple things and use bundles to group
UDFs.
> 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)
