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

Ariel Weisberg commented on CASSANDRA-11935:
--------------------------------------------

bq. I am not convinced that it make sense, as that ticket has been committed 
since 22 months, but feel free to do it.
How does time since a commit landed in any way impact the significance of any 
issues that might exist with it? Especially when it is sitting in an unreleased 
version that no one is using so you can't even point to the fact that no one 
has complained about it as evidence that it might be good enough?

bq. I assume, the relevance is why you haven't articulated your concerns during 
the last 2 1/4 years since the ticket's been worked on. It's harsh to reopen a 
ticket that's been quiet for nearly two years with a justification like I 
personally prefer this default behaviour
The person you are responding to wasn't even working on Cassandra for most of 
that time. And even if they were it's still unreasonable to expect everyone on 
the project to keep tabs on everything that happens in every single JIRA and 
commit. Everyone comes across issues with changes as they are doing other work 
and it's fine to address them as they are discovered.

This is not a case of personal preference. This is not a style question. It's a 
public API and a question of correctness and a silent implicit behavior 
resulting in data loss. Documentation isn't necessarily a fix if there is an 
approach available that doesn't cause loss.

I also have questions about how overflow is handled. Can a user detect if 
overflow occurred?

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to