Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

etcdctl: endpoint hash command #8348

Closed
heyitsanthony opened this issue Aug 1, 2017 · 3 comments
Closed

etcdctl: endpoint hash command #8348

heyitsanthony opened this issue Aug 1, 2017 · 3 comments
Labels
area/performance

Comments

@heyitsanthony
Copy link
Contributor

Support hashing the KV store through etcdctl.
@heyitsanthony heyitsanthony mentioned this issue Aug 1, 2017
Closed
@heyitsanthony
Copy link
Contributor Author

heyitsanthony commented Aug 1, 2017 •
edited
Loading

This should also include an update to op-guide/v2-migration.md with an example to check the hashes if there are TTLs

@gyuho
Copy link
Contributor

gyuho commented Aug 1, 2017

I am also interested, for play.etcd.io.

Should we also expose Hash API to clientv3 and go from there?
Then adding hash field to StatusResponse?
Or just separate wrapper in clientv3 for HashResponse.

@heyitsanthony
Copy link
Contributor Author

@gyuho I'm hesitant to change StatusResponse to include data that's not returned by the status RPC. Just HashKV(int64) (*HashKVResponse, error) under the maintenance interface should be OK.

@gyuho gyuho mentioned this issue Aug 2, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/performance
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gyuho @heyitsanthony