[
https://issues.apache.org/jira/browse/CASSANDRA-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594779#comment-14594779
]
Aleksey Yeschenko commented on CASSANDRA-9542:
----------------------------------------------
nit: "Functions from system keyspace are resolved before logged keyspace."
should be "Functions from the system keyspace are resolved before functions in
the current keyspace.". 'logged' is not used in {{CQL.textile}}
In {{CreateAggregateStatement}} there is no reason for {{stateType}} to be a
field, can be a local variable.
Otherwise looks ok.
> 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
>
> Attachments: 9542.txt
>
>
> 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)
