jsonb mutation variable fails with "no such type exists in the schema: 'jsonb'"

Connected to Hasura through a WebSocket, I’m trying to use a jsonb column, inserting an array. But even without any data being sent for that variable (which should then result in it becoming NULL since it’s nullable), I still get an error stating no such type exists in the schema: 'jsonb'. I’ve seen jsonb being used in the Hasura docs (as an example: https://hasura.io/docs/1.0/graphql/core/mutations/insert.html#insert-an-object-with-a-jsonb-field) so I’m not sure what I’m doing wrong.

Here’s the mutation (note that I’m not sending the $files variable through for testing purposes):

mutation submitPost($body: String!, $files: jsonb) {
  insert_newsfeed_one(object: { body: $body }) {
    id
  }
}

Here’s the full WS message being sent:

{
  "id": "5",
  "type": "start",
  "payload": {
    "variables": { "body": "Testing", "files": [] },
    "extensions": {},
    "operationName": "submitPost",
    "query":"mutation submitPost($body: String!, $files: jsonb) {
      insert_newsfeed_one(object: {body: $body}) {
        id
        __typename
      }
    }
    "
  }
}

And the error response:

{
  "type": "error",
  "id": "5",
  "payload": {
    "errors": [
      {
        "extensions": {
          "path": "$.variableValues",
          "code": "validation-failed"
        },
        "message": "no such type exists in the schema: 'jsonb'"
      }
    ]
  }
}

[tirumaraiselvan]

Hi @trymbill

Are you using any role (x-hasura-role)? If you are using a role, then does the table with a jsonb column have permission on that column to insert or select? I guess it does not by looking at the error message: no such type exists in the schema: 'jsonb'

This is just a GraphQL spec thing where if a type is not used in any field, it is simply omitted from schema. You do not see this with GraphiQL as it is running as admin role.

[trymbill]

Ahh! Good catch! Yeah, it’s definitely a new column so the permissions weren’t updated yet. Thank you for your help!

Just as a sidenote; might be worth updating that error message. Checking the permissions will from now on be something I check, but for new users, it’s definitely not 100% obvious. Thanks again for a killer product!