Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84A5B10758 for ; Tue, 3 Mar 2015 08:41:14 +0000 (UTC) Received: (qmail 61613 invoked by uid 500); 3 Mar 2015 08:41:04 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 61570 invoked by uid 500); 3 Mar 2015 08:41:04 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 61558 invoked by uid 99); 3 Mar 2015 08:41:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2015 08:41:04 +0000 Date: Tue, 3 Mar 2015 08:41:04 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7875) Prepared statements using dropped indexes are not handled correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344738#comment-14344738 ] Aleksey Yeschenko commented on CASSANDRA-7875: ---------------------------------------------- Thanks for looking into it. I'm leaning towards leaving 2.0 alone, but not sure. [~thobbs] ? > Prepared statements using dropped indexes are not handled correctly > ------------------------------------------------------------------- > > Key: CASSANDRA-7875 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7875 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Tyler Hobbs > Assignee: Stefania > Priority: Minor > Fix For: 2.1.4 > > Attachments: prepared_statements_test.py, repro.py > > > When select statements are prepared, we verify that the column restrictions use indexes (where necessary). However, we don't perform a similar check when the statement is executed, so it fails somewhere further down the line. In this case, it hits an assertion: > {noformat} > java.lang.AssertionError: Sequential scan with filters is not supported (if you just created an index, you need to wait for the creation to be propagated to all nodes before querying it) > at org.apache.cassandra.db.filter.ExtendedFilter$WithClauses.getExtraFilter(ExtendedFilter.java:259) > at org.apache.cassandra.db.ColumnFamilyStore.filter(ColumnFamilyStore.java:1759) > at org.apache.cassandra.db.ColumnFamilyStore.getRangeSlice(ColumnFamilyStore.java:1709) > at org.apache.cassandra.db.PagedRangeCommand.executeLocally(PagedRangeCommand.java:119) > at org.apache.cassandra.service.StorageProxy$LocalRangeSliceRunnable.runMayThrow(StorageProxy.java:1394) > at org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1936) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > {noformat} > During execution, we should check that the indexes still exist and provide a better error if they do not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)