You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2012/11/26 18:48:58 UTC
[jira] [Resolved] (CASSANDRA-4991) "Keys must not be empty" error
on secondary indexing.
[ https://issues.apache.org/jira/browse/CASSANDRA-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna resolved CASSANDRA-4991.
-------------------------------------
Resolution: Duplicate
The fix for this should be in the upcoming 1.1.7.
> "Keys must not be empty" error on secondary indexing.
> -----------------------------------------------------
>
> Key: CASSANDRA-4991
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4991
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Environment: cassandra 1.1.6
> oracle jdk 1.7.09
> Reporter: Chuan-Heng Hsiao
>
> Encounter the following error message:
> INFO [OptionalTasks:1] 2012-11-13 14:24:20,650 ColumnFamilyStore.java
> (line 659) Enqueuing flush of
> Memtable-(some_cf).(some_cf)_(some_idx)_idx_1@1216346401(485/8360
> serialized/live bytes, 24 ops)
> ERROR [FlushWriter:2123] 2012-11-13 14:24:20,650
> AbstractCassandraDaemon.java (line 135) Exception in thread
> Thread[FlushWriter:2123,5,main]
> java.lang.AssertionError: Keys must not be empty
> at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:133)
> at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:176)
> at org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:295)
> at org.apache.cassandra.db.Memtable.access$600(Memtable.java:48)
> at org.apache.cassandra.db.Memtable$5.runMayThrow(Memtable.java:316)
> at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> When inserting the data, I set the default value as '' for all
> pre-defined columns. I suspect that it is the reason for this error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira