You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2016/09/23 16:59:20 UTC

[jira] [Updated] (CASSANDRA-12654) Query Validation Error : CQL IN operator over last partitioning|clustering column (valid) is rejected if a query fetches collection columns

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

Benjamin Lerer updated CASSANDRA-12654:
---------------------------------------
    Assignee:     (was: Benjamin Lerer)

> Query Validation Error : CQL IN operator over last partitioning|clustering column (valid) is rejected if a query fetches collection columns
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12654
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12654
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Samba Siva Rao Kolusu
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 3.8, 3.9, 3.10, 4.0
>
>
> although IN operator is allowed over the last clustering or partitioning columns, the CQL Query Validator is rejecting queries when they attempt to fetch collection columns in their result set.
> It seems a similar bug (CASSANDRA-5376) was raised some time ago, and a fix (rather mask) was provided to give a better error message to such queries in 1.2.4. 
> Considering that Cassandra & CQL has evolved a great deal from that period, it now seems possible to provide an actual fix to this problem, i.e. allowing queries to fetch collection columns even when IN operator is used.
> please read the following mail thread to understand the context : 
> https://lists.apache.org/thread.html/8e1765d14bd9798bf9c0938a793f1dbc9c9349062a8705db2e28d291@%3Cuser.cassandra.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)