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

FederatedStore to send unsupported operations to subgraphs #2823

Closed
GCHQDev404 opened this issue Nov 15, 2022 · 0 comments · Fixed by #2824
Closed

FederatedStore to send unsupported operations to subgraphs #2823

GCHQDev404 opened this issue Nov 15, 2022 · 0 comments · Fixed by #2824
Assignees
Labels
enhancement Improvement to existing functionality/feature federated-store Specific to/touches the federated-store module

Comments

@GCHQDev404
Copy link
Contributor

Describe the new feature you'd like
FederatedStore to send unsupported operation to sub-graphs

Why do you want this feature?
Improves federation.
Means the federated store will send operations it doesn't understand to sub-graphs.

@GCHQDev404 GCHQDev404 added the enhancement Improvement to existing functionality/feature label Nov 15, 2022
@GCHQDev404 GCHQDev404 added this to the v2.0.0-alpha-0.4 milestone Nov 15, 2022
GCHQDev404 added a commit that referenced this issue Nov 15, 2022
@n3101 n3101 added the federated-store Specific to/touches the federated-store module label Nov 16, 2022
GCHQDev404 added a commit that referenced this issue Nov 16, 2022
#2824)

* gh-2823 FederatedStore unsupported operations are forwarded to subgraphs.

* gh-2823 FederatedStore unsupported operations are forwarded to subgraphs. Tests

* gh-2823 FederatedStore unsupported operations are forwarded to subgraphs. improvements

Co-authored-by: GCHQDev404 <GCHQDev404@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement to existing functionality/feature federated-store Specific to/touches the federated-store module
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants