[
https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184839#comment-13184839
]
Sylvain Lebresne commented on CASSANDRA-3634:
---------------------------------------------
If we are trading some (one time) additional work on the driver's author to
support prepared statement against a potential 10%, I'd be in favor of the
binary approach (given that prepared statement are an optimization for
performance in the first place, and without saying that we shouldn't care about
making driver's author life as easy as possible).
Now I'd mention that I think the binary approach is actually more problematic
for custom comparators, because drivers will need to expose a way for the user
to either say how to pack their strings, or to directly provide pre-serialized
binary. Which then put a little more burden on the user (of course the user
knows of to serialize the strings for his custom comparator since he write the
comparator, but this means a duplication of code for him, possibly in multiple
languages, which is no fun).
> 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
