[
https://issues.apache.org/jira/browse/CASSANDRA-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154083#comment-15154083
]
Robert Stupp commented on CASSANDRA-10818:
------------------------------------------
Yep, such an interface would be fine and I'll adopt the code to provide such a
thing. That could also be used to provide additional information about the
client, the connection, the user and so on (just brain-dumping, nothing to add
to this ticket).
> Evaluate exposure of DataType instances from JavaUDF class
> ----------------------------------------------------------
>
> Key: CASSANDRA-10818
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10818
> Project: Cassandra
> Issue Type: New Feature
> Components: CQL
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 3.x
>
>
> Currently UDF implementations cannot create new UDT instances.
> There's no way to create a new UT instance without having the
> {{com.datastax.driver.core.DataType}} to be able to call
> {{com.datastax.driver.core.UserType.newValue()}}.
> From a quick look into the related code in {{JavaUDF}}, {{DataType}} and
> {{UserType}} classes it looks fine to expose information about return and
> argument types via {{JavaUDF}}.
> Have to find some solution for script UDFs - but feels doable, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
