[
https://issues.apache.org/jira/browse/CASSANDRA-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787977#comment-17787977
]
Andres de la Peña commented on CASSANDRA-18926:
-----------------------------------------------
Thanks, here is the identical PR for trunk:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2920]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3319/workflows/d776ba63-ee96-4e5f-8654-297485a49ea0]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3319/workflows/bb6712b8-971d-4843-a475-4e51ec83b9ab]|
> 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: 20m
> 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]
