What means SUBSCHEMA_TYPE_CHANGED?

[MrDiba]

I'm experimenting with Apicurio registry and I have created an JSON artifact in which I have inserted multiple versions. Looking like this:

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "User",
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "favorite_number": {
      "type": [
        "integer",
        "null"
      ]
    },
    "favorite_color": {
      "type": [
        "string",
        "null"
      ]
    }
  },
  "required": [
    "name"
  ]
}

During one of the versions I didn´t copy the first { resulting in an incorrect JSON, but it accepted it.

Now if I want to create an new version to create an valid JSON again I receive an SUBSCHEMA_TYPE_CHANGED and it doesn´t allow me to create an new version.

I tried searching the documentation and the code on what SUBSCHEMA_TYPE_CHANGED means but I could not figure it out.

Maybe someone can enlighten me on what the error means and how I can fix it?

[jsenko]

During one of the versions I didn´t copy the first { resulting in an incorrect JSON, but it accepted it.

Can you give me the content so I can reproduce it? What were your rule settings?

Also your latest version content and the schema that is causing the error would help, as I need two schemas to see what has caused the compatibility check failure. I guess that it means that somewhere value of "type" in a property schema has changed. It is also possible that you've added a "type" where there wasn't one before.

[EricWittmann]

Also the full response from the REST API call that is failing would be useful. That should have more information in it than just SUBSCHEMA_TYPE_CHANGED hopefully...

[jsenko]

There is also an open issue to improve the error messages #5066 , so we're tracking this problem.