[
https://issues.apache.org/jira/browse/CASSANDRA-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999813#comment-13999813
]
Sylvain Lebresne commented on CASSANDRA-6975:
---------------------------------------------
Just to be clear, I'm too fussed about the fact that the paging call is not
used, it's just convenient to have it here for when we'll need it and I'm sure
we will at some point. The main point of the linked branch is to use prepared
statement in SystemKeyspace. Which is at least reasonably useful for paxos as
it avoid serializing every mutation that goes through paxos into a hex string
(it's also nice to skip parsing every time for other system queries, even
though that's probably not a huge deal in practice).
> 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)
