ApolloGateway doesn't recognize federation-jvm hosted graphql

_query { _service { sdl } } on federation-jvm gives

{
  "errors": [],
  "data": {
    "_service": {
      "sdl": "schema {\n  query: Query\n}\n\ntype Query {\n  me: User\n}\n\ntype User @key(fields : \"id\") {\n  id: ID!\n  name: String\n  username: String\n}\n"
    }
  },
  "extensions": null,
  "dataPresent": true
}

while ApolloGateway is expecting a different format with the same schema.grapql file:

{
  "data": {
    "_service": {
      "sdl": "extend type Query {\n  me: User\n}\n\ntype User @key(fields: \"id\") {\n  id: ID!\n  name: String\n  username: String\n}\n"
    }
  }
}

https://github.com/apollographql/federation-demo/blob/master/services/accounts/index.js#L4

ApolloGateway doesn’t like the empty Array in .errors. ApolloGateway considers this as not having a schema, and it also complains when having schema {\n query: Query\n}\n\n in sdl.

Once the sdl string is patched and the empty array .errors is removed, the Graphql schema defined in federation-jvm starts to appears on ApolloGateway.

snippet to patch the sql string:

final String modified = sdl.replace("schema {\n  query: Query\n}\n\n", "");
_service.put("sdl", modified);

[yuhanz]

The first part is a non-issue in the spring-example. (.errors:[] was introduced because we serialized ExecutionResult directly.)

So, the only problem is with the schema {\n query: Query\n} in the sdl

[sachindshinde]

@kenshih @areidt84 @omarsallah00 I believe your issues are similar to #23 , which ended up being a bug in graphql-java’s SchemaPrinter. We’ve patched their printer in federation-jvm v0.3.4 and above, let me know if you’re still experiencing issues and I can reopen this issue.