Cannot have more than one Root Field Namespace

[hongbo-miao]

Version Information

Server Version: graphql-engine:v2.5.0.cli-migrations-v3

Environment

What is the expected behaviour?

I have two remote schemas. I try to set Root Field Namespace for both of them.

Keywords

Root Field Namespace

What is the current behaviour?

I can set first Root Field Namespace for first remote schema successfully.

However, when I set for second remote schema, it failed with error

Found conflicting definitions for "Query". The definition at "query_root.hm_graphql_server" differs from the the definition at "query_root.hm_dgraph".

Screenshots or Screencast

[hongbo-miao]

I tried to manually add two root_fields_namespace in the remote_schemas.yaml file and then load by metadata migration.

- name: hm-dgraph-schema
  definition:
    url: http://dgraph-dgraph-alpha.hm-dgraph:8080/graphql
    timeout_seconds: 60
    customization:
      root_fields_namespace: hm_dgraph # <--
    forward_client_headers: true
  comment: ""
- name: hm-graphql-server-schema
  definition:
    url: http://graphql-server-service.hm:31800/graphql
    timeout_seconds: 60
    customization:
      root_fields_namespace: hm_graphql_server # <--
    forward_client_headers: true
  comment: ""

The server will crash. So seems right now Hasura does not support adding namespaces for more than one remote schemas.

[paritosh-08]

Closed via 25a027b

This issue was due to the conflicting root field type names, so HGE will now automatically prefix the root field type names with the root field namespace. Please note that you can change the root field type name by choosing appropriate type name mapping.