cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6975) Allow usage of QueryOptions in CQLStatement.executeInternal
Date Thu, 03 Apr 2014 10:15:16 GMT

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

Sergio Bossa commented on CASSANDRA-6975:
-----------------------------------------

Is it possible to backport this patch to 2.0 as well?

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

Mime
View raw message