Skip to content

Support Distributed Mutations via GraphQL #32

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

Closed
manishrjain opened this issue Feb 17, 2016 · 1 comment
Closed

Support Distributed Mutations via GraphQL #32

manishrjain opened this issue Feb 17, 2016 · 1 comment
Assignees
Labels
kind/feature Something completely new we should consider.
Milestone

Comments

@manishrjain
Copy link
Contributor

manishrjain commented Feb 17, 2016

Mutations via GraphQL which I introduced recently, won't work the same way as our bulk loader does. Because these mutations would need to go over the network; while our bulk loader, even in distributed state, does not. The general idea to do mutations is as follows:

Step 1: Network calls to assign Uids for all Xids.

Step 2: Distributed based on predicates, and multiple network calls to reach all corresponding servers. One RPC each server to load up the edges.

Step 3: Wait for success. If success, return or run the query part of GraphQL.
In case of failure, return to client; and let them retry. Later, we can add a retry loop here. Note that without transactions, some of these would have been applied; without any particular way to revert their changes (potential overwrites over data before this change was made). *

  • The transactional behaviour would fall under distributed transactions, which we don't intend to support at least until v1.0. So, for now, we'll have this issue where a failure would result in some unapplied RDFs -- in general, until distributed transactions, we don't provide atomicity over multiple RDFs. Each RDF is applied atomically; and independently from others.
@manishrjain manishrjain added kind/feature Something completely new we should consider. graphql labels Feb 17, 2016
@manishrjain manishrjain self-assigned this Feb 17, 2016
@manishrjain manishrjain added this to the v0.2 milestone Feb 17, 2016
@manishrjain manishrjain changed the title Support Distributed Mutation via GraphQL Support Distributed Mutations via GraphQL Feb 17, 2016
@manishrjain
Copy link
Contributor Author

Distributed mutations now work.

@manishrjain manishrjain added the kind/feature Something completely new we should consider. label Mar 22, 2018
danielmai pushed a commit that referenced this issue May 1, 2020
shivaji-kharse pushed a commit that referenced this issue Mar 12, 2024
* restart running trivy security scans
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Something completely new we should consider.
Development

No branches or pull requests

1 participant