typesense

My cluster (<http://gxu1iajypedl2z0tp-1.a1.typesense.net|gxu1iajypedl2z0tp-1.a1.typesense.net>) turned into unhealthy.
Any ways to fix this issue? If there are documentations about this, it will be helpful :smile:

Could you share the exact collection schema you used?

```{
        'name': 'users',
        'fields': [
          {'name': 'displayName', 'type': 'string' },
          {'name': 'userId', 'type': 'string' },
          {'name': 'favGameTitle1','optional':'true', 'type': 'string' },
      
          {'name': 'gender', 'optional':'true', 'type': 'int32' },

        ],
        'default_sorting_field': 'gender'
      }```

After adding optional parameter, the cluster might stop working.

Ah, so the issue is that Typesense crashed because there's an uncaught exception in the json parsing around boolean values, in Typesense core.

We currently expect `optional` to have values of `true` or `false`. Looks like a string value of `"true"` for optional crashes the server :disappointed:

We'll fix the bug shortly, in the meantime could you use bool values instead of string values for `true` and `false` in the schema?

Now to recover the node, we'd unfortunately need to clear the bad data in the server... Would that be ok?

(Separately we're also working on a way to skip over bad data in v0.20, so having to clear data when bad data makes it in, is only an issue with v0.19)

&gt; Now to recover the node, we'd unfortunately need to clear the bad data in the server... Would that be ok?
Could you confirm that you're ok with this <@U01RU41DMPF>

Sorry, I'd need explicit confirmation that you're ok with me clearing the data on the node and then restart the server

Could you reply with an explicit OK to clear the data?

Sorry about that! Bug fix for the original issue should be out in v0.20 soon

Hi <@U01RU41DMPF> I've upgraded this cluster to v0.20, now that it's out. It should be largely transparent to you!

Thank you so much:laughing::laughing::tada:

And finally our team has decided to use Typesense:blush: