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.

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

Implement lock component to manage access to shared resources #564

Closed
danoscarmike opened this issue Jul 6, 2017 · 1 comment
Closed
Assignees
Labels
api: spanner Issues related to the Spanner API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release.

Comments

@danoscarmike
Copy link
Contributor

Hi Dave, issue to track rolling our own lock component. Can you please update this issue with an ETC? Thanks!

@vkedia @michaelbausor @bjwatson

@danoscarmike danoscarmike added api: spanner Issues related to the Spanner API. priority: p0 Highest priority. Critical issue. P0 implies highest priority. labels Jul 6, 2017
@dwsupplee
Copy link
Contributor

Hey Dan,

Right now, we are looking at next friday (7/14). Will keep you posted if anything changes!

@michaelbausor michaelbausor added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed priority: p0 Highest priority. Critical issue. P0 implies highest priority. labels Jul 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the Spanner API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release.
Projects
None yet
Development

No branches or pull requests

3 participants