Persisting Error while Dropping Field from Collection
TLDR Atul is struggling with recurrent errors when trying to drop a field from a collection. Jason advised to open a GitHub issue documenting the problem.
Aug 08, 2023 (1 month ago)
Atul
03:11 PMI don't know why I am getting strange errors when I am trying to drop a field from my collection.
{
"message": "Field `my_another_field` has been declared in the schema, 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`."
}This is really strange. I am struggling since 1 hour on it. I just have to drop a field but getting this error continuously.
Atul
03:12 PMThis is definitely a new Bug/issue.
Jason
03:34 PMhttps://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
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.
Fixing "bad json" error in Typesense 0.24
Adam experiences "bad json" error when creating collections in Typesense 0.24. Jason identifies a typo in the docs causing the error and helps troubleshoot additional errors.
5Troubleshooting Collection Schema and Upsert Issue in Typesense
David was having trouble upserting data with id in Typesense. Jason clarified that 'id' didn't need to be included in the schema and suggested a correct approach for specifying unindexed fields. The issue was resolved when David identified a mistake related to the output format from Postgres.
2