[
https://issues.apache.org/jira/browse/CASSANDRA-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787340#comment-17787340
]
Andres de la Peña commented on CASSANDRA-18926:
-----------------------------------------------
Here I'm porting a patch by [~jasonstack], with some additions for vector
indexes:
||PR||CI||
|[5.0
|https://github.com/apache/cassandra/pull/2918]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3316/workflows/088b952c-12b5-4f61-b2d8-591ac1349298]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3316/workflows/5e0c07a4-0e3f-4489-a021-d357e53b5bd9]|
Writes exceeding the configured max term size will be accepted but ignored by
the index with both client and log warnings.
I'll add the PR for trunk if it looks good, it should be mostly identical.
> SAI in-memory index does not include maximum term size check when adding terms
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-18926
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18926
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
> Reporter: Mike Adamson
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 5.0-beta
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{SSTableIndexWriter}} rejects terms that exceed a maximum term size with
> a no-spam warning, but the {{TrieMemoryIndex}} does not do this.
> We should check term sizes when rows are added and issue client warnings when
> this happens. This still needs to happen in the {{SSTableIndexWriter}} to
> handle terms during an initial index build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
