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

Multi-object etcd transactions #2904

Closed
bgrant0607 opened this issue Dec 12, 2014 · 4 comments
Closed

Multi-object etcd transactions #2904

bgrant0607 opened this issue Dec 12, 2014 · 4 comments
Labels
area/etcd priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@bgrant0607
Copy link
Member

This is a tracking issue.
etcd-io/etcd#860
@bgrant0607 bgrant0607 added kind/enhancement area/etcd priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Dec 12, 2014
@simon3z simon3z mentioned this issue Mar 27, 2015
Closed
@mikedanese
Copy link
Member

https://github.com/coreos/etcd/blob/master/Documentation/rfc/v3api.md

@mikedanese mikedanese added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. team/control-plane and removed team/master labels Aug 20, 2015
@bgrant0607 bgrant0607 mentioned this issue Aug 26, 2015
Closed
@bgrant0607 bgrant0607 mentioned this issue Feb 12, 2016
Open
@ericchiang ericchiang mentioned this issue May 17, 2016
Merged
@timothysc
Copy link
Member

I'm going to close this issue. Multi-op transactions exist in v3, but we will wait until 1.7 before we start batching some operations.

@0xmichalis
Copy link
Contributor

I'm going to close this issue. Multi-op transactions exist in v3, but we will wait until 1.7 before we start batching some operations.

Shouldn't we keep the issue open until we get there?

@timothysc
Copy link
Member

timothysc commented Dec 10, 2016 •
edited
Loading

We have a series of other issues on our roadmap. This specific issue simply referenced an etcd capability, and not the refactoring of the registry and storage layers which is what is required to leverage the capability that now exists in etcd3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/etcd priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@timothysc @mikedanese @0xmichalis @bgrant0607