[
https://issues.apache.org/jira/browse/CASSANDRA-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482366#comment-13482366
]
Edward Capriolo commented on CASSANDRA-3799:
--------------------------------------------
I understand the challenges.
I think that building things that only python's cqlsh can do is bad form. These
things are not going to work for all clients, and this will hurt the language.
We will be into a thrift like world where those using hector have tools to work
with data (like composites) and those using another language may not.
Do you really think CQL will never have functions? I think sooner or later
someone is going to ask for trim() or setContains() or whatever. I think they
make the schema-less users much happier and can be a big part of the language
in the future.
> cqlsh: ASSUME should also change how values are sent to cassandra
> -----------------------------------------------------------------
>
> Key: CASSANDRA-3799
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3799
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.3
>
>
> cqlsh's ASSUME command currently only changes how query *return* values are
> deserialized, and never transforms user CQL text before sending to Cassandra.
> Apparently cassandra-cli also changes how values are interpreted and
> marshaled for Cassandra, so user expectation is that cqlsh should also do
> this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
