cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10818) Evaluate exposure of DataType instances from JavaUDF class
Date Tue, 12 Apr 2016 21:58:25 GMT


Tyler Hobbs commented on CASSANDRA-10818:

[~snazy] the new changes look great!

Would you mind rebasing on the latest trunk and re-running the tests?  I think the rebase
should be straightfoward except for one thing from CASSANDRA-7423: the {{CQLTester.userType()}}
function now takes alternating {{fieldName, fieldValue}} arguments.

Other than that, in {{CQL.textile}}, the changes section needs a new entry.  I think that's

> Evaluate exposure of DataType instances from JavaUDF class
> ----------------------------------------------------------
>                 Key: CASSANDRA-10818
>                 URL:
>             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

View raw message