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

Benedict commented on CASSANDRA-11935:
--------------------------------------

I'm not so sure - and perhaps this is something to raise in the other 
discussion around JIRA process.  I'll make a note to bring it up in that 
meeting (that currently has very few likely attendees - please let me know if 
you want me to put you on the list!)

I don't want to divert the conversation too much, but I think questions that go 
to the heart of the semantics of a ticket should live on the original ticket.  
This isn't a bug, or a follow-up, it suggests the ticket was never really 
'done' to the community's endorsement (or, at least, we haven't yet established 
if it was)

> Add support for arithmetic operators
> ------------------------------------
>
>                 Key: CASSANDRA-11935
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11935
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: CQL
>            Reporter: Benjamin Lerer
>            Priority: Major
>             Fix For: 4.0
>
>
> The goal of this ticket is to add support for arithmetic operators:
> * {{-}}: Change the sign of the argument
> * {{+}}: Addition operator
> * {{-}}: Minus operator
> * {{*}}: Multiplication operator
> * {{/}}: Division operator
> * {{%}}: Modulo operator
> This ticket we should focus on adding operator only for numeric types to keep 
> the scope as small as possible. Dates and string operations will be adressed 
> in follow up tickets.
> The operation precedence should be:
> # {{*}}, {{/}}, {{%}}
> # {{+}}, {{-}}
> Some implicit data conversion should be performed when operations are 
> performed on different types (e.g. double + int).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to