[
https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187859#comment-13187859
]
Jonathan Ellis commented on CASSANDRA-3634:
-------------------------------------------
bq. If we settle on ByteBuffer as the encoding of arguments then I believe we
must accompany it with a indicator of how it was encoded. Without it, on the
server side we will have to trust that the caller encoded the argument to
exactly match the proper encoding for the validator or comparator used in the
Term.
I don't see why we need to add extra complexity here. Trusting the client to
encode correctly is what we've done on the Thrift side for years.
> 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
