cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3036) Vague primary key references in CQL
Date Wed, 17 Aug 2011 17:36:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Yaskevich updated CASSANDRA-3036:
---------------------------------------

    Attachment: CASSANDRA-3036.patch

> 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
>    Affects Versions: 0.8.1
>            Reporter: Kelley Reynolds
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>              Labels: cql
>             Fix For: 0.8.5
>
>         Attachments: CASSANDRA-3036.patch
>
>
> 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

        

Mime
View raw message