[
https://issues.apache.org/jira/browse/CASSANDRA-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729189#comment-14729189
]
Adam Holmberg commented on CASSANDRA-9952:
------------------------------------------
Yes, it works in 3.0 because {{argument_names}} is {{frozen<list<text>>}} in
3.0, while in 2.2 it is just {{list<text>}}, so an empty list returns null. I'm
not sure why the types are defined differently in the server schema metadata,
but we should accommodate this.
https://datastax-oss.atlassian.net/browse/PYTHON-392
> UDF with no parameters prevents cqlsh DESCRIBE from working
> -----------------------------------------------------------
>
> Key: CASSANDRA-9952
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9952
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: ubuntu 64 bit, using ccm tool with a one node cluster,
> release 2.2.0
> Reporter: Jim Meyer
> Priority: Minor
> Fix For: 2.2.x
>
> Attachments: test_9952.py
>
>
> If I create a user defined function that takes no parameters like this:
> cqlsh:test> CREATE FUNCTION no_parm() CALLED ON NULL INPUT RETURNS bigint
> LANGUAGE java AS 'return System.currentTimeMillis() / 1000L;';
> The function works fine in queries, but in cqlsh the describe command stops
> working:
> cqlsh:test> DESC KEYSPACE test;
> izip argument #1 must support iteration
> If I drop the function, then describe starts working normally again. It
> appears describe assumes there is at least one argument for UDF's, but
> creating and using the functions does not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
