[
https://issues.apache.org/jira/browse/CASSANDRA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015562#comment-13015562
]
Eric Evans commented on CASSANDRA-2409:
---------------------------------------
If you raise a RuntimeException from the lexer or parser, it will not be
propagated down to the client (it's swallowed and turned into an internal
server error).
If you look at the revised patch, I moved the size equality test and conversion
to Map into {{UpdateStatement.getColumns()}} where an
{{InvalidRequestException}} can be raised (everything that calls
{{getColumns()}} already throws {{InvalidRequestException}}.
> Add INSERT support to CQL
> -------------------------
>
> Key: CASSANDRA-2409
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2409
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 0.8
>
> Attachments: CASSANDRA-2409.patch,
> v1-0001-CASSANDRA-2409-CQL-INSERT-implementation.txt
>
>
> There are two reasons to support INSERT:
> - It helps new users feel comfortable (everyone's first statement will be to
> try to INSERT something, we should make that a positive experience instead of
> slapping them)
> - Even though it is synonymous with update it is still useful in your code to
> have both to help communicate intent, similar to choosing good variable names
> The only downside is explaining how INSERT isn't a "true" insert because it
> doesn't error out if the row already exists -- but we already have to explain
> that same concept for UPDATE; the cognitive load is extremely minor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
