Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
Docs
Description
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
Attachments
Attachments
Issue Links
- is depended upon by
-
CASSANDRA-7563 UserType, TupleType and collections in UDFs
- Resolved
-
CASSANDRA-7737 Update CQL doc for UDF
- Resolved
-
CASSANDRA-7458 functional indexes
- Open
-
CASSANDRA-7391 Partial indexes
- Open
-
CASSANDRA-7562 Java source code for UDFs
- Resolved
-
CASSANDRA-7556 Update cqlsh for UDFs
- Resolved
- is related to
-
CASSANDRA-7557 User permissions for UDFs
- Resolved
-
CASSANDRA-7708 UDF schema change events/results
- Resolved
-
CASSANDRA-7924 Optimization of Java UDFs
- Resolved
-
CASSANDRA-7526 Defining UDFs using scripting language directly from CQL
- Resolved
-
CASSANDRA-7674 Add implicit casting of UDF arguments
- Resolved
-
CASSANDRA-7677 UDF stdlib
- Resolved
- relates to
-
CASSANDRA-7697 UDF use new schema migration
- Resolved