[
https://issues.apache.org/jira/browse/CASSGO-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Reis updated CASSGO-119:
-----------------------------
Source Control Link:
https://github.com/apache/cassandra-gocql-driver/commit/9bc3b5dee806f1847db37262c5ec510d2f417140
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Add PreparedMetadata and IsPrepared to ObservedQuery and ObservedBatch
> ----------------------------------------------------------------------
>
> Key: CASSGO-119
> URL: https://issues.apache.org/jira/browse/CASSGO-119
> Project: Apache Cassandra Go driver
> Issue Type: Improvement
> Components: Core
> Reporter: Raj Ummadisetty
> Assignee: Raj Ummadisetty
> Priority: Normal
> Fix For: 2.2.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently, ObservedQuery and ObservedBatch do not expose the keyspace or
> table targeted by a query. Consumers (metrics collectors, loggers, tracers)
> have to parse the CQL statement string to extract that information.
> Add a nested PreparedMetadata struct (Keyspace, Table) on ObservedQuery and a
> parallel []PreparedMetadata on ObservedBatch, populated from prepared
> statement metadata returned by Cassandra. Pair these with an IsPrepared bool
> / []bool so consumers can distinguish prepared statements (where the metadata
> is valid) from statements that take the unprepared path (DDL, etc.), where
> the metadata is the zero value.
> No additional round-trips or CQL parsing, the metadata is already available
> internally via the prepared-statement response used for routing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
