You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/06/04 01:25:39 UTC
[jira] [Commented] (CASSANDRA-9542) Create UDA does not recognize
built-in functions without specifying system keyspace
[ https://issues.apache.org/jira/browse/CASSANDRA-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571828#comment-14571828 ]
Robert Stupp commented on CASSANDRA-9542:
-----------------------------------------
Short evaluation: method {{o.a.c.cql3.statements.CreateAggregateStatement#validateFunctionKeyspace}} should not blindly assume the {{USE}} keyspace but instead try to look up a native function (in {{system}} KS) first and try {{USE}} keyspace next (same semantic used for looking up functions for execution).
> Create UDA does not recognize built-in functions without specifying system keyspace
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-9542
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9542
> Project: Cassandra
> Issue Type: Bug
> Reporter: Zachary Kurey
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 2.2.x
>
>
> I'd expect when creating a UDA not to have to specify the system keyspace when using a built-in function for the state or final function. For example:
> {code}
> CREATE AGGREGATE if not exists ks.my_agg(int)
> SFUNC ks.adder
> STYPE int
> FINALFUNC intasblob
> ;
> {code}
> Gives me me the error:
> {quote}Final function ks.intasblob(int) does not exist or is not a scalar function{quote}
> Prefixing with 'system.' fixes the issue. But I was expecting it to resolve as if I were using a built in function elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)