You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/12/05 00:50:10 UTC
[jira] [Commented] (CASSANDRA-10818) Evaluate exposure of DataType
instances from JavaUDF class
[ https://issues.apache.org/jira/browse/CASSANDRA-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042440#comment-15042440 ]
Tyler Hobbs commented on CASSANDRA-10818:
-----------------------------------------
Our alternative is to use the new method for creating UDT values that will be introdued by [JAVA-1012|https://datastax-oss.atlassian.net/browse/JAVA-1012]. However, that might end up being more complicated for a user to work with.
> 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
>
> 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)