[
https://issues.apache.org/jira/browse/CASSANDRA-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598292#comment-13598292
]
Aleksey Yeschenko edited comment on CASSANDRA-3799 at 3/10/13 3:52 PM:
-----------------------------------------------------------------------
It is now (post-1.2.2) both easier and much less important. As Paul mentioned,
we do parse every query already, but I haven't looked into how difficult
rewriting them would be (the only rewriting we do atm is adding a defult limit
to SELECTs).
I'll take a look, and if it turns out to be easy-ish, I say let's to it. And if
not.. there are more important issues out there.
was (Author: iamaleksey):
It is now (post-1.2.2) both easier and much less important. As Paul
mentioned, we do parse every query now, but I haven't looked into how difficult
rewriting them would be.
I'll take a look, and if it turns out to be easy-ish, I say let's to it. And if
not.. there are more important issues out there.
> 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
>
> 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
