[
https://issues.apache.org/jira/browse/CASSANDRA-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984087#comment-16984087
]
Edward Capriolo commented on CASSANDRA-15082:
---------------------------------------------
Why is it 5? Could it be a variable? Could it be an option when creating the
table? Why or why not?
It hard to a close it as a duplicate when no one is engaging with either ticket
in a meaningful way. Can anyone actually use this feature without a read before
write? It seems like the risk is fairly high that someone could accidentally
with a forloop send the same row 5 times and hopeless corrupt the table.
> SASI SPARSE mode 5 limit
> ------------------------
>
> Key: CASSANDRA-15082
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15082
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/SASI
> Reporter: Edward Capriolo
> Priority: Normal
>
> I do not know what the "improvement" should be here, but I ran into this:
> [https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/index/sasi/disk/OnDiskIndexBuilder.java#L585]
> Term '55.3' belongs to more than 5 keys in sparse mode, which is not allowed.
> The only reference I can find to the limit is here:
> [http://www.doanduyhai.com/blog/?p=2058]
> Why is it 5? Could it be a variable? Could it be an option when creating the
> table? Why or why not?
> This seems awkward. A user can insert more then 5 rows into a table, and it
> "works". IE you can write and you can query that table getting more than 5
> results, but the index will not flush to disk. It throws an IOException.
> Maybe I am misunderstanding, but this seems impossible to support, if users
> inserts the same value 5 times, the entire index will not flush to disk?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
