Unable to use several dgraph instances together with GraphQL federation

[matthewmcneely]

Discussed in https://github.com/orgs/dgraph-io/discussions/9659

^{Originally posted by 1Maxnet1 March 17, 2026}
As already discussed here: https://discuss.dgraph.io/t/cannot-use-apollo-federation-with-multiple-dgraph-instances/15562 dgraph automatically generates helper types when loading a GraphQL schema. When I now want to compose a supergraph for two dgraph instances, I am unable to composite schema (e.g. with apollo-rover or hive cli) to load into my gateway. Is there any possibility to deactivate the generation of helper types to allow to federate multiple graph databases?

[matthewmcneely]

@1Maxnet1 I pushed a test image to our custom docker hub repo with what I hope is a fix for this. Can you test with this image tag: dgraph/dgraph-custom:v25.3.1-preview-federation-changes?

We don't maintain a federated graph here and our federation integration tests are minimal. I believe the code solves your immediate problems, but wanted to let you test it out on a real-world federated graph before we release this.

FYI, here's the PR from which this preview image was built: #9663

[1Maxnet1]

Can you test with this image tag: dgraph/dgraph-custom:v25.3.1-preview-federation-changes?

Thanks a lot for the fast implementation of a fix! I just tested locally the composition, which works now. Now that composition is working, I'll continue to create my federated setup and report back how it goes.

[github-actions]

This issue has had no activity for 60 days and has been marked stale. Comment to keep it active.