[
https://issues.apache.org/jira/browse/CASSANDRA-17735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569757#comment-17569757
]
Ekaterina Dimitrova commented on CASSANDRA-17735:
-------------------------------------------------
It seems there were some environmental issues - I just resubmitted the 4.1
[upgrade
tests|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1793/workflows/951fd90a-618d-4156-91d1-559cb144d6cb],
also one of the [cqlsh
jobs|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1793/workflows/8e7db3b0-f847-428e-91df-eca838d09185/jobs/13345]
The rest seems like known issues.It is interesting I see second time the
simulator tests, one failing. I will open a ticket for that one but it is not
related to this patch
> Fix issues with index_summary_resize_interval and index_summary_capacity
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-17735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17735
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.0.x, 4.1-beta, 4.x
>
>
> There are a few problems:
> 4.0+:
> * the virtual table displays only the cassandra.yaml values for both
> properties, all changes after startup are not updated
> 4.1+:
> * Breaking compatibility - -1 was considered disabled, this should be
> considered as null now for the new config. The converter should be updated.
> There is a test for the -1, disable but it didn't caught the issue because of
> the previous issue mentioned (the disconnect between jmx and the actual
> property in Config class)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
