You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be desirable for the client to be able to know the Couchbase server version of the nodes it is connected to. This would be useful for determining if a particular feature is available or not. Also, consuming applications, projects could have additional requirements.
Cluster version information is available using the http://localhost:8091/pools/default. An example for parsing the response can be seen here.
Considerations:
Minimum compatibility cluster version
Per node server version
Caching behaviour (default time + ability to override / force refresh)
Version information (major, minor, patch, build and edition)
The text was updated successfully, but these errors were encountered:
MikeGoldsmith
changed the title
Cluster version information
Server / Cluster version information
Jun 23, 2017
I think thats a great idea, and java has this already to varying degrees (i.e. we use it for test setup internally to figure out which tests to run). Other parts are exposed on the management APIs for retrieval purposes.
What could make sense is to collect the status quo for our SDKs and see what we currently have (and in parallel of course define where we want to be :)) 👍
Yeah, agree we should use what the SDKs already have implemented and see if it fits all of use-cases. I'll make a start on the RFC to find out what we already have.
It would be desirable for the client to be able to know the Couchbase server version of the nodes it is connected to. This would be useful for determining if a particular feature is available or not. Also, consuming applications, projects could have additional requirements.
Cluster version information is available using the
http://localhost:8091/pools/default
. An example for parsing the response can be seen here.Considerations:
The text was updated successfully, but these errors were encountered: