[
https://issues.apache.org/jira/browse/CASSGO-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Reis updated CASSGO-101:
-----------------------------
Source Control Link:
https://github.com/apache/cassandra-gocql-driver/commit/eb7c7208cac84795c5cea903ee7eaef04b7d58d8
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Support custom listeners for NodeState, TopologyChange and SchemaChange
> events
> -------------------------------------------------------------------------------
>
> Key: CASSGO-101
> URL: https://issues.apache.org/jira/browse/CASSGO-101
> Project: Apache Cassandra Go driver
> Issue Type: New Feature
> Components: Core
> Reporter: Bohdan Siryk
> Assignee: Bohdan Siryk
> Priority: Normal
> Fix For: 2.1.0
>
> Time Spent: 22h 20m
> Remaining Estimate: 0h
>
> Originally raised here:
> [https://the-asf.slack.com/archives/C05LPRVNZV1/p1767548766531679]
> Currently, gocql doesn't expose an API for end-users to track Cassandra
> events related to node state, topology, and schema changes. There are a
> couple of usecases when we want to listen for those events, for example, for
> monitoring purposes.
> To implement this, we can add listener fields to the
> [ClusterConfig.Events|https://github.com/apache/cassandra-gocql-driver/blob/f1e31a58f7e0c25e58e2e2a0a0c6de358e643e8b/cluster.go#L206-L213]
> subtype for schema, topology, and node state changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]