[
https://issues.apache.org/jira/browse/CASSANDRA-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999108#comment-13999108
]
Aleksey Yeschenko commented on CASSANDRA-6975:
----------------------------------------------
With CASSANDRA-6065 pushed to 3.0, it's kinda being obsoleted by
CASSANDRA-6230. And the batchlog will be singnificantly rewritten with
CASSANDRA-7237.
That said, both would benefit from paging in 2.1 still, because we need to run
some startup conversion for both BM and HHOM to get rid of any
MessagingVersion.12-serialised mutations, so that we can drop that code (incl.
some leftover supercolumn code) in 3.0.
> Allow usage of QueryOptions in CQLStatement.executeInternal
> -----------------------------------------------------------
>
> Key: CASSANDRA-6975
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6975
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Mikhail Stepura
> Assignee: Mikhail Stepura
> Priority: Minor
> Fix For: 2.1 rc1
>
> Attachments: cassandra-2.1-executeInternal.patch
>
>
> The current implementations of {{CQLStatement.executeInternal}} accept only
> {{QueryState}} as a parameter. That means it's impossible to use prepared
> statements with variables for internal calls (you can only pass the variables
> via {{QueryOptions}}). We also can't use the internal paging in internal
> "SELECT" statements for the very same reason.
> I'm attaching the patch which implements that.
> [~slebresne] [~iamaleksey] what do you think guys?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
