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

Jonathan Ellis commented on CASSANDRA-2475:
-------------------------------------------

bq. My opinion on string vs. binary is largely unchanged here. String 
parameters is the path of greatest abstraction, eliminating a proven vector for 
bugs, and it keeps our query interface as friendly as possible. 

While I agree in principle, from CASSANDRA-1788, CASSANDRA-3333, and others, 
we've seen that reducing copies really matters to CPU-bound queries.  So I 
would expect the same here; convert-from-string is basically a glorified copy.

We're already doing binary data for resultsets, so I don't think the bar for 
client developers gets much higher if we use them for prepared statements.
                
> Prepared statements
> -------------------
>
>                 Key: CASSANDRA-2475
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2475
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>    Affects Versions: 1.0.5
>            Reporter: Eric Evans
>            Assignee: Rick Shaw
>            Priority: Minor
>              Labels: cql
>             Fix For: 1.1
>
>         Attachments: 2475-v1.patch, 2475-v2.patch, 
> v1-0001-CASSANDRA-2475-prepared-statement-patch.txt, 
> v1-0002-regenerated-thrift-java.txt
>
>


--
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

        

Reply via email to