Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <13772063.476441282335018903.JavaMail.jira@thor>
Date: Fri, 20 Aug 2010 16:10:18 -0400 (EDT)
From: "Nate McCall (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1410) allow index expressions on
 columns that are not part of the resultset
In-Reply-To: <27953041.449101282234216378.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nate McCall commented on CASSANDRA-1410:
----------------------------------------

Merge issue on CHANGES.txt otherwise applies cleanly. Unit and nosetests for test_index_scan pass

> allow index expressions on columns that are not part of the resultset
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-1410
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1410
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.7 beta 2
>
>         Attachments: 1410.txt
>
>
> Currently, any expressions that apply to columns that are not pulled in by the resultset slicepredicate are ignored.  While it's inefficient to have to add or remove columns to the predicate on the fly, I see this becoming a major source of user confusion otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.