#community-help

Issue with Deleting Documents Using Base64 String IDs in Typesense

TLDR Sean faced issues deleting documents with base64 string IDs in Typesense. Jason clarified that the error was fixed in newer versions, suggesting collection deletion and reindexing as a solution.

19mo

Join the chat

Jun 16, 2022 (19 months ago)

Photo of md5-2d5361393096e40eccbe0d4cfa49f7de

Sean

07:36 PM

So I have been using object Ids that were a base64 string of some text as my ids for document creation.

This is causing issues trying to delete the document from the collection for any id that contains a forward slash. Why?
This is the error I get.
Funny thing is a can edit the document just fine

07:41

Sean

07:41 PM

I have now switched to using uuid for the id generation but what to do about the 90K documents that I did wrong…?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

08:10 PM

Hmm, may I know which version of Typesense this is on?

Sean

08:52 PM

Jason

09:10 PM

Ah, we've fixed this issue in the latest versions... Unfortunately there's no way to delete these docs in v0.21.0, except for deleting the collection and reindexing

Typesense

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

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Deleting and Creating Documents in Typesense

Priyank asked for help with deleting and creating documents in Typesense and found the problem to be an issue with their own code. Jason offered support.

11mo

Effective Document Deletion Strategies in Typesense

Adrian asked about deleting potentially non-existent documents. Pantelis suggested using IDs for document deletion or queries within delete function. Adrian decided to use query-based deletions.

4mo

Issue with Typesense Schema and Ruby Client

Mateo faces issues while creating a schema and using Ruby client for Typesense. Jason suggests using a new field instead of 'id' and provides assistance for Ruby client errors.

10mo