cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3634) compare string vs. binary prepared statement parameters
Date Thu, 12 Jan 2012 17:13:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185071#comment-13185071
] 

Sylvain Lebresne edited comment on CASSANDRA-3634 at 1/12/12 5:13 PM:
----------------------------------------------------------------------

bq.  that's the case for a String-based api as well as a binary one.

For String-based, the translation from String->binary would happen server side, where we
do have the custom comparator and thus the fromString() method (which have to be written from
the comparator anyway). With binary, you would have to write the comparator.fromString(),
but also have the same client side.

Of course, that is if the client has its customely-comparable prepared statement parameters
in a string form to begin with.

On the other side, taking binary would likely make it much more easier to take binary data
(like pictures), without forcing a binary->string client-side followed by a string->binary
decoding server side. Which is probably a bigger deal than the custom comparator thingy now
that I think of that.

So (and unless I don't understand anything on this issue and what's above is completely false),
I'm clearly in favor of binary.
                
      was (Author: slebresne):
    bq.  that's the case for a String-based api as well as a binary one.

For String-based, the translation from String->binary would happen server side, where we
do have the custom comparator and thus the fromString() method (which have to be written from
the comparator anyway). With binary, you would have to write the comparator.fromString(),
but also have the same client side.
                  
> 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

        

Mime
View raw message