Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 14 Aug 2011 19:26:27 +0000 (UTC)
From: "Kelley Reynolds (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <67373191.37430.1313349987199.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CASSANDRA-3036) Vague primary key references in
 CQL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Vague primary key references in CQL
-----------------------------------

                 Key: CASSANDRA-3036
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3036
             Project: Cassandra
          Issue Type: Bug
          Components: API
            Reporter: Kelley Reynolds
            Priority: Minor


create columnfamily wonk (id 'utf8' primary key, id int)
update wonk set id=1 where id='test'
create index wonk_id on wonk (id)

This does what you would expect but then the results are unclear when using 'id' in a where clause.

"select * from wonk where id=1" returns nothing and "select * from wonk where id='test'" works fine.

Perhaps secondary indexes should not be allowed on columns that have the same name as the key_alias? At least a warning or something should be thrown to indicate you've just made a useless index.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira