Hi team! Why is it impossible to create non-indexed, but required, field?

Historically the required field has always been applied for only those that are part of the index. So if a field is marked as required, it cannot be non indexed.

Got it, thank you

But we will likely fix it

It would be great for our case Also, it is possible to disable auto-schema (?) for nested fields? I have an

object

field with

index: false

in the schema and when I add documents in the index, typesense creates nested fields definitions

Can you please create an issue with a reproduceable example. This sounds like a bug than feature request

Could you please take a look: https://gist.github.com/b0g3r/11e51a25a56c3e34859e12585788d4ef Maybe it’s expected behaviour

Technically index: false fields should not be added to schema. I presume the same thing works fine for a non-nested field right?

should not be added to schema

But what about non-indexed required fields? Let me create two issues, one for tracking non-optional non-indexed field and one for unexpected nested fields schema

Following up here to see if a resolution was reached? Running into the same issue in 0.25.1