Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 14 Jun 2017 06:18:00 +0000 (UTC)
From: "Samrat Gandotra (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13079661.1497421021000.14616.1497421080056@Atlassian.JIRA>
In-Reply-To: <JIRA.13079661.1497421021000@Atlassian.JIRA>
References: <JIRA.13079661.1497421021000@Atlassian.JIRA> <JIRA.13079661.1497421021497@jira-lw-us.apache.org>
Subject: [jira] [Created] (CASSANDRA-13599) Filtering on Secondary Index
 throws out of memory error even with limit 1 and mentioning the partition
 key in the where clause.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 14 Jun 2017 06:18:08 -0000

Samrat Gandotra created CASSANDRA-13599:
-------------------------------------------

             Summary: Filtering on Secondary Index throws out of memory error even with limit 1 and mentioning the partition key in the where clause.
                 Key: CASSANDRA-13599
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13599
             Project: Cassandra
          Issue Type: Bug
         Environment: Using Cassandra 3.10 on Windows 7
            Reporter: Samrat Gandotra


We have used secondary index on a column with very low cardinality.
So if we use partition key and any secondary index value ( value which has millions of corresponding rows in the table) in the where clause with limit 1 even then it takes lot of time to respond and atlast out of memory error occurs.

The correct scenario should be that if we are mentioning a very small limit like 1 then the results should be shown immediately when the secondary index and partition key is used in the where clause.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org