[ 
https://issues.apache.org/jira/browse/CASSANDRA-17029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436346#comment-17436346
 ] 

Kanthi Subramanian commented on CASSANDRA-17029:
------------------------------------------------

{code:java}
// code placeholder
case INTEGER:

    switch (nt)

    {

        case BIGINT:

        case COUNTER:

        case DATE:

        case DECIMAL:

        case DOUBLE:

        case DURATION:

        case FLOAT:

        case INT:

        case SMALLINT:

        case TIME:

        case TIMESTAMP:

        case TINYINT:

        case VARINT:

            return AssignmentTestable.TestResult.WEAKLY_ASSIGNABLE;
{code}
Looks like both bigint and timestamp gets the WEAKLY_ASSIGNABLE when the 
parameter is integer.

> Add unix time conversion functions
> ----------------------------------
>
>                 Key: CASSANDRA-17029
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17029
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL/Syntax
>            Reporter: Benjamin Lerer
>            Assignee: Kanthi Subramanian
>            Priority: Normal
>
> It will be useful to have some functions to conver unix time values into C* 
> native types, like:
> *     {{toDate(bigint)}} 
> *     {{toTimestamp(bigint)}}
> *     {{mintimeuuid(bigint)}}
> *     {{maxtimeuuid(bigint)}}
> +Additional info for newcomers:+
> Those new functions need to be added to 
> {{org.apache.cassandra.cql3.functions.TimeFcts}} and some unit tests need to 
> be added to {{org.apache.cassandra.cql3.functions..TimeFctsTest}}. The other 
> functions in {{TimeFcts}} provide some good example of how to create new 
> functions.
> As it is a new functionality they need to be mentioned in the {{NEWS.txt}} 
> file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to