#community-help

Resolving Error Code 400 Issue with Updating Collection Schema

TLDR sahubar encountered an error when updating the scheme in production. Kishore Nallan suggested emailing Typesense and mentioned the ability to create a new updated collection, but sahubar insisted on using the existing collection.

1mo

Join the chat

Aug 18, 2023 (1 month ago)

Photo of md5-41ca8b93efee2249950bdd80b036a9dc

sahubar

11:31 AM

Hi Jason Kishore Nallan
Error: e: Request failed with HTTP code 400 | Server said: Field rating has been declared as a default sorting field, but is not found in the documents already present in the collection. If you still want to add this field, set it as optional: true.
It seems an error throws when I update the scheme in the collection
Note: This schema update working fine stage environment but the production environment throws above mentioned error response

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

11:45 AM

Please email [email protected] with the cluster ID and the collection you are trying this on.

sahubar

12:13 PM

I have sent the email, need to deploy a live build so please do the needful earliest

Kishore Nallan

12:21 PM

I'm in a couple of calls, and this requires us to investigate what's happening so won't be able to get to this until a bit later.

12:22

Kishore Nallan

12:22 PM

If you are blocked and need to deploy a build you can create a new collection with the updated schema and sync your data

sahubar

12:38 PM

OK Kishore Nallan but we are using existing collection only not the new collection

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2786 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Updating Collection Schema on Typesense Cloud Returns 408 Error

Rushil had issues updating a schema on Typesense Cloud, receiving a 408 error. Jason assisted, indicating that his cluster upgrade caused the issue, solved it, and advised to avoid similar changes in the future.

2mo

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.

2mo

Troubleshooting Typesense 400 Error with Null Fields

sonu was encountering a 400 error due to null fields during Typesense indexing. Jason suggested upgrading to a recent version, removing null fields, and marking potentially null fields as `optional: true`. gab shared a similar issue and workaround.

29mo