You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/04/02 22:37:19 UTC
[jira] [Commented] (CASSANDRA-6975) Allow usage of QueryOptions in
CQLStatement.executeInternal
[ https://issues.apache.org/jira/browse/CASSANDRA-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958143#comment-13958143 ]
Aleksey Yeschenko commented on CASSANDRA-6975:
----------------------------------------------
Haven't looked at the patch itself yet (and I'd rather volunteer Sylvain to review it), but generally it would be nice to have this - for HHOM and for BathlogManager, too, esp. with the planned improvements to it.
> 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 beta3
>
> 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)