[
https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188336#comment-13188336
]
Sylvain Lebresne commented on CASSANDRA-3634:
---------------------------------------------
bq. 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.
I think we could send enough info with the CqlPreparedResult, i.e, replace the
count by a list of types, like what we do for CqlResult. It would be simpler
for drivers than keeping the full schema somewhere and probably parse the
initial prepared query to figure out to what each marker correspond in the
schema.
There would be the slight issue of someone changing the validation of a given
value between preparation and execution, but I don't think it's a big deal at
all to say that you'll have to re-prepare queries if you do that (how often do
you actually change a value validation function anyway, and even if you do so,
you'd better change it for something that is compatible with the previous type
for CQL, so in fact most changes would not be a problem).
> 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
