Issue with In-Place Schema Changes and Querying New Field
TLDR Ricardo faced issues querying a new field after in-place schema change. The problem was due to an older Python client, which was resolved by updating it.
Jun 22, 2023 (5 months ago)
Since version 0.23
Schema changes: we now support fields to be added or dropped from a collection schema in-place.
We're trying to add a new field, and query by it. But it seems that we are not able to query by it. We can add it though, but then can't use it in a query. Is there any limitation on in-place changes?
Indexed 3011 threads (79% resolved)
Updating Collection Schema and Querying Unspecified Fields in Typesense
Stefan asked about updating a collection schema. Kishore Nallan stated it's not currently possible but suggested automatic schema detection in version 0.20. Rishabh sought a workaround and Jason suggested creating a new collection with a new schema and re-indexing the data. Rishabh also asked about defining custom field IDs which Jason confirmed is not possible with Typesense.
Modifying Schema and Inserting JSON Fields in Typesense
Sai inquired about modifying the schema and inserting a JSON field after creation, to which Kishore Nallan replied these requests are in backlog and shared a potential timeline for one of them. Additionally, Kishore Nallan suggested a solution for a query issue Sai was facing.
Issue with Query Hangs Identifying Different Collection Field Names
Kanak experiences query hangs when collection field names differ. Ahmed had an issue adding documents to collections, which was self-resolved. Kishore Nallan resolved Kanak's issue with the updated build.