[
https://issues.apache.org/jira/browse/CASSANDRA-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022698#comment-17022698
]
Jordan West commented on CASSANDRA-15469:
-----------------------------------------
Good catch [~djoshi]. I think these could be addressed storing the cache size
in a field and updating it on every call to {{reset()}}. The buffer allocation
issue could be addressed by reallocating when a difference in the size of the
buffer and the expected size given the current field value is detected. WDTY?
One issue I see tangentially related to this is that updating the value doesn't
affect the existing cached indexes. I think its safe to assume that an operator
can drop the cache if needed but I'd like to check w/ [~clohfink] here if
something more heavy handed is desired re: existing cached items when updating
the cache size property.
> IndexInfo/ColumnIndex Refactors & Cleanup
> -----------------------------------------
>
> Key: CASSANDRA-15469
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15469
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/SSTable
> Reporter: Jordan West
> Assignee: Jordan West
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Changes determined by audit of IndexInfo and ColumnIndex changes for
> Cassandra 4.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
