[
https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188092#comment-13188092
]
Rick Shaw commented on CASSANDRA-3634:
--------------------------------------
Yes. That is all exactly what I meant to say... ;-)
It can all be done on the client side if you have the full current schema
available which, of course, is doable but expensive (in time) to get in place.
{{ResultSet}} needs similar info so there may be some sharing that can take
place but I haven't really looked yet.
Validation, transformation, or corrective action could be done on the server
side if you knew how it was encoded in the first place; hence my suggestion.
> compare string vs. binary prepared statement parameters
> -------------------------------------------------------
>
> Key: CASSANDRA-3634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3634
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Eric Evans
> Priority: Minor
> Labels: cql
> Fix For: 1.1
>
>
> Perform benchmarks to compare the performance of string and pre-serialized
> binary parameters to prepared statements.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
