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.
Aug 18, 2023 (1 month ago)
Error: e: Request failed with HTTP code 400 | Server said: Field
ratinghas 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
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
Kishore Nallan11:45 AM
Kishore Nallan12:21 PM
Kishore Nallan12:22 PM
Indexed 2786 threads (79% resolved)
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.
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.
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.