Typesense rocks my friends! 😃 Now, I just got a question regarding the id field. I read that if the field is a string and does not contain characters that would require URL encoding, the id field would actually be used to identify a document. Correct? It just happened that in order to update a document I upserted a document with the same exact id. And it seems like it created a second entry... How do I know if the id field is actually used as the actual document identifier? What would you recommend in my case? Currently running with these versions: https://cdn.jsdelivr.net/npm/algoliasearch@4.5.1/dist/algoliasearch-lite.umd.js https://cdn.jsdelivr.net/npm/instantsearch.js@4.8.3/dist/instantsearch.production.min.js https://cdn.jsdelivr.net/npm/typesense-instantsearch-adapter@1.2.1-7/dist/typesense-instantsearch-adapter.min.js

field is a string and does not contain characters that would require URL encoding, the id field would actually be used to identify a document. Correct?

That's correct. Could you do one or more search(es) that will return these two items? That will include the ID field in the response

Does it need to be through the API or could I do it manually in the cloud db interface?

Sure, you can do it in the cloud search interface as well

OK!

You can then look at the network requests in the browser to the see the exact API response

OK perfect

Yeah it will show you the IDs used or assigned

👍

In the browser's dev tools, under the network tab

😅Sure, and in the API response, where do I look to check the actual identifier?

If you search for an API call to

multi_search

, then click on the "Preview" for that response, and expand

results

, then

hits

and then the

document

object inside each hit

OK, I FOUND IT. It's a space that I forgot to trim at the end of the ID!!!

Didn't get you... Could you give me an example?

Trying to delete the dupe there is an error - what do you suggest?

the document identifier would actually be a auto-generated id, right?

Correct.

Would I see this identifier in each document?

Yup.

What would its name be?

It will be called

id

and it will be an incrementing number

So we would have 2 fields named "id" then?

No, if there is a field called

id

in the document that will be used as the identifier field

Ok then!

Trying to delete the dupe there is an error - what do you suggest?

Could you post the full JSON of this document you're trying to delete?

Does this help?

Hmm, I think this might be a bug. To confirm, could you try deleting this document via the API?

Let's see... but it seems like we hit the actual problem of having a char that is URL encodable... the space character!

Could you open a Github issue for this, with a minimal replicateable example?

OK, but what it the start of the URL to send the DELETE request to?

Your Typesense cluster hostname

OK

Something like

<https://xxx-1.a1.typesense.net>

curl -X DELETE https://cloud.typesense.org/clusters/1ow83v9khrefbpump/collections/arts/documents/ART41554-4742%20 But I guess I need to identify, 'cause the above did not work

The URL would be https://1ow83v9khrefbpump-1.a1.typesense.net/collections/arts/documents/ART41554-4742%20

OK got it

Yeah, this is a bug. Could you create a Github issue for it?

OK I will

Since you're using Typesense Cloud, could you email support@typesense.org with your cluster ID? We can then upgrade your cluster to this RC build

No, don't have a dev/staging anymore