[
https://issues.apache.org/jira/browse/CASSANDRA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197037#comment-14197037
]
Aleksey Yeschenko commented on CASSANDRA-8189:
----------------------------------------------
It's there to properly handle dropped indexes. We can't just insert a string
'null' value, because, for one, that would break upgrading, and, for two,
doesn't make much sense.
CASSANDRA-6717 moves index definitions into a separate table, so I'm marking
this issue as duplicate of that instead.
In the meantime you can increase the warning threshold.
> tombstone WARN in log file when creating a table with many columns
> ------------------------------------------------------------------
>
> Key: CASSANDRA-8189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8189
> Project: Cassandra
> Issue Type: Bug
> Reporter: Oded Peer
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Attachments: LargeTableTest.java
>
>
> I created a table with 500 columns, creating the table resulted in a warning
> in the log file.
> bq. WARN 10:13:17 Read 2504 live and 1003 tombstoned cells in
> system.schema_columns (see tombstone_warn_threshold). 2147483647 columns was
> requested, slices=[table_0-table_0:!],
> delInfo={deletedAt=-9223372036854775808, localDeletion=2147483647}
> See the attached unit test.
> I analyzed the table to understand what are the tombstone columns and it
> appears that Cassandra creates deleted columns for "index_type" and
> "index_name" if they are not present for a column.
> "index_type" get the String value "null" if it is not present.
> A side effect is that these deleted columns are not removed. Since
> system.schema_columns rarely changes compaction never happens for this table
> and the sstable will retain the deleted columns.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
