You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "DOAN DuyHai (JIRA)" <ji...@apache.org> on 2016/03/21 16:17:25 UTC

[jira] [Created] (CASSANDRA-11392) Add IMPORT block or auto import java.util for UDF code block

DOAN DuyHai created CASSANDRA-11392:
---------------------------------------

             Summary: Add IMPORT block or auto import java.util for UDF code block
                 Key: CASSANDRA-11392
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11392
             Project: Cassandra
          Issue Type: Improvement
          Components: CQL
         Environment: C* 3.4
            Reporter: DOAN DuyHai


Right now, when creating Java source code for UDF, since we cannot define import, we need to use fully qualified class name, ex:


{noformat}
CREATE FUNCTION toSet(li list<text>)
CALLED ON NULL INPUT
RETURNS text
LANGUAGE java
AS $$
    java.util.Set<String> set = new java.util.HashSet();
    for(String txt: list) {
        set.add(txt);
    }
    return set;
$$;
{noformat}

Classes from {{java.util}} package are so commonly used that it makes developer life easier to import automatically {{java.util.*}} in the {{JavaUDF}} base class so that developers don't need to use FQCN for common classes.

 The only drawback I can see is the risk of class name clash but since:

1. it is not allow to create new class
2. classes that can be used in UDF are restricted

 I don't see serious clash name issues either

[~snazy] WDYT ?
 



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