cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-7875) Prepared statements using dropped indexes are not handled correctly
Date Wed, 03 Sep 2014 21:06:51 GMT
Tyler Hobbs created CASSANDRA-7875:

             Summary: Prepared statements using dropped indexes are not handled correctly
                 Key: CASSANDRA-7875
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Tyler Hobbs
            Assignee: Tyler Hobbs
            Priority: Minor
             Fix For: 1.2.19, 2.0.11, 2.1.1

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:

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
	at org.apache.cassandra.db.filter.ExtendedFilter$WithClauses.getExtraFilter(
	at org.apache.cassandra.db.ColumnFamilyStore.filter(
	at org.apache.cassandra.db.ColumnFamilyStore.getRangeSlice(
	at org.apache.cassandra.db.PagedRangeCommand.executeLocally(
	at org.apache.cassandra.service.StorageProxy$LocalRangeSliceRunnable.runMayThrow(
	at org.apache.cassandra.service.StorageProxy$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

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

View raw message