#community-help

Resolving ID Type Warnings and Ensuring Unique Documents

TLDR Mubashirullah asked about providing their own ID, which led to a discussion with Kishore Nallan about warnings, schemas, and preventing document repetition.

25mo

Join the chat

Dec 22, 2021 (25 months ago)

Photo of md5-cea7a558edb0c66a1c07dfdcf00bc141

Mubashirullah

06:08 AM

I was under the impression I can provide my own id. Its of type string.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

06:09 AM

Use another name like my_id

Mubashirullah

06:09 AM

I used searchable_id like you suggested. I have both id and searchable_id

Kishore Nallan

06:10 AM

Yeah then don't need to add ID to the schema. It's an implicit field. Or just ignore that warning, it's not an error just a warning.

Mubashirullah

06:11 AM

Cool. If I enter the same documents again, will it know its a repetition? upsert

Kishore Nallan

06:11 AM

So long you use the same ID field

Mubashirullah

06:11 AM

Thank you.

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

Adding ID Field to Index and Schema Retrospectively

Zach asked about adding an ID field in the schema without altering existing documents. Jason suggested creating a new field called `id_search` for this purpose.

6mo

Resolving 'Cannot use `id` as a query by field' error in Typesense

Alberto was encountering a 'Cannot use `id` as a query by field' error in Typesense. Jason clarified that the 'id' field is used internally and suggested duplicating data in a new field for searching.

1mo

Resolving TS Issue on Id Field and Search Results

Mubashirullah had issues getting the 'id' field from their schema, which Kishore Nallan explained was due to it being a special identifier in TS 0.22. They recommended creating a 'searchable_id' field.

25mo