Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Server / Cluster version information #71

Open
MikeGoldsmith opened this issue Jun 23, 2017 · 2 comments
Open

Server / Cluster version information #71

MikeGoldsmith opened this issue Jun 23, 2017 · 2 comments
Assignees

Comments

@MikeGoldsmith
Copy link
Contributor

MikeGoldsmith commented Jun 23, 2017

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)
@MikeGoldsmith MikeGoldsmith changed the title Cluster version information Server / Cluster version information Jun 23, 2017
@daschl
Copy link
Contributor

daschl commented 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 :)) 👍

@MikeGoldsmith
Copy link
Contributor Author

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.

@MikeGoldsmith MikeGoldsmith self-assigned this Jun 27, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants