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

Allow modifying relation tuples with consistency guarantees #328

Closed
zepatrik opened this issue Nov 19, 2020 · 2 comments
Closed

Allow modifying relation tuples with consistency guarantees #328

zepatrik opened this issue Nov 19, 2020 · 2 comments
Assignees
Labels
feat New feature or request. rfc A request for comments to discuss and share ideas. stale Feedback from one or more authors is required to proceed.

Comments

@zepatrik
Copy link
Member

Is your feature request related to a problem? Please describe.

A client might require transaction like consistency guarantees across multiple read/write/... operations.

Describe the solution you'd like

There could be an atomic update write request that takes the old and new version of a relation tuple. It deletes the old version and inserts the new version.
Other more flexible transaction approaches might get very complicated.

Describe alternatives you've considered

  1. Require the clients to manage locking somehow and don't provide any feature like this.
  2. Allow a client to acquire a lock and reject every request from other client instances until the lock is free.
  3. Provide consistency information using etag. Clients are then free to decide how they react if there was a change.
@zepatrik zepatrik added feat New feature or request. rfc A request for comments to discuss and share ideas. labels Nov 19, 2020
@robinbraemer robinbraemer self-assigned this Nov 19, 2020
@zepatrik zepatrik added the corp/m6 Up for M6 at Ory Corp. label Mar 29, 2021
@github-actions
Copy link

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan on resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneous you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Mar 30, 2022
@zepatrik zepatrik removed stale Feedback from one or more authors is required to proceed. corp/m6 Up for M6 at Ory Corp. labels Mar 30, 2022
@github-actions
Copy link

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request. rfc A request for comments to discuss and share ideas. stale Feedback from one or more authors is required to proceed.
Projects
None yet
Development

No branches or pull requests

2 participants