You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Bohdan Siryk (Jira)" <ji...@apache.org> on 2026/10/07 10:10:00 UTC

[jira] [Updated] (CASSGO-132) Disabled Metadata Cache Prevents KeyspaceChanged events

     [ https://issues.apache.org/jira/browse/CASSGO-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bohdan Siryk updated CASSGO-132:
--------------------------------
    Status: Ready to Commit  (was: Changes Suggested)

> Disabled Metadata Cache Prevents KeyspaceChanged events
> -------------------------------------------------------
>
>                 Key: CASSGO-132
>                 URL: https://issues.apache.org/jira/browse/CASSGO-132
>             Project: Apache Cassandra Go driver
>          Issue Type: Bug
>          Components: Core
>            Reporter: James Hartig
>            Assignee: Bohdan Siryk
>            Priority: Normal
>             Fix For: 2.2.0
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> When metadata caching is disabled after CASSGO-104 HostSelectionPolicy's no longer has it's KeyspaceChanged called. There's also no panic or documentation or warning about this. If metadata caching is enabled then synthetic events are fired instead of real events that come from Cassandra. There isn't a way to restore the previous behavior or only getting server-side events. Documentation still claims they're only fired for server-side events which is not true.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org