Resolving 504 Errors During Schema Updates
TLDR David faced an issue with schema update resulting in 504 errors. The issue resolved itself. Jason explained the reason behind the errors.
Aug 02, 2023 (1 month ago)
I tried to update a schema in my dev env to enable infix search on one of our primary fields. I received two
504s in the cloud console, and now it appears my entire collection is gone. I'm also unable to create a new one in my cluster. Not sure what's going on here, any guidance? Thanks
It appears despite the
504responses, the schema is now updated and my documents are back online. I didn't see anything indicating that something was processing, but that's what I was hoping.
Indexed 2764 threads (79% resolved)
Unexpected Schema Updates in Typesense Cloud
Samuel encountered unexpected schema updates in Typesense Cloud, which they didn't make. Jason asked for more information to investigate the issue.
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.
Updating Existing Schema Error in UI
Dev encountered an error while updating a schema through the UI. Jason explained that creating a new collection with the updated schema is necessary to change the setting.