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
{{ message }}
This repository has been archived by the owner on Oct 7, 2023. It is now read-only.
I did a quick search through the zk*.go source to see whether zetcd's schema will tamper with an already existing etcd schema. Afaict, it looks like zetcd writes the ZooKeeper schema to /zk on the etcd endpoint. Is this the case?
If not, is it possible to specify the base key for the schema to something like /zk?
Or if so, would it be difficult to add the ability to specify the base key to something other than /zk? Would all one need to do would be to modify zketcd_path.go?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I did a quick search through the
zk*.go
source to see whether zetcd's schema will tamper with an already existing etcd schema. Afaict, it looks like zetcd writes the ZooKeeper schema to/zk
on the etcd endpoint. Is this the case?If not, is it possible to specify the base key for the schema to something like
/zk
?Or if so, would it be difficult to add the ability to specify the base key to something other than
/zk
? Would all one need to do would be to modifyzketcd_path.go
?The text was updated successfully, but these errors were encountered: