[
https://issues.apache.org/jira/browse/CASSANDRA-14275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-14275:
------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.x)
4.0
Status: Resolved (was: Patch Available)
Committed to 4.0 as [5dc55e715eba6667c388da9f8f1eb7a46489b35c
|https://github.com/apache/cassandra/commit/5dc55e715eba6667c388da9f8f1eb7a46489b35c].
> Cassandra Driver should send identification information to Server
> -----------------------------------------------------------------
>
> Key: CASSANDRA-14275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14275
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Dinesh Joshi
> Assignee: Dinesh Joshi
> Priority: Major
> Fix For: 4.0
>
>
> Currently there doesn't seem to be any way to readily identify the driver
> that clients are using to connect to Cassandra. Add the capability of
> identifying the driver through metadata information much like how HTTP
> Clients identify themselves through User-Agent HTTP header. This is useful
> for debugging in large deployments where clients tend to use different
> drivers, wrappers and language bindings to connect to Cassandra. This can
> help surface issues as well as help detect clients which are using older or
> unsupported drivers.
> The identification information should be a string that unambiguously
> identifies the driver. It should include information such as the name of the
> driver, it's version, CQL version, Platform (Linux, macOS, Windows, etc.) and
> architecture (x86, x86_64).
> We should surface this information in `nodetool clientstats` command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
