Creating Unique ID from URL Field in Typesense DB
TLDR andy wanted to make the 'url' field the 'id' in typesense DB. Kishore Nallan advised that the 'id' field is always the ID by convention, but andy could duplicate the content as 'id', rename it, or use the 'url' field as 'id'.
1
Dec 13, 2022 (10 months ago)
andy
10:43 AMKishore Nallan
10:49 AMid
field. By convention the field named id
is always the ID. If you want the url
field to be the identifier, duplicate the content as id
.andy
10:50 AMandy
10:50 AM1
Kishore Nallan
10:51 AMid
is a special field so you can't search on it.andy
10:51 AMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Understanding Document ID Fields and Rectifying Duplicate Document Error
John queried about understanding document ID fields and fixed a duplication issue with guidance from Jason. They discovered a bug preventing document deletion due to a URL encodable character, with John opening a GitHub issue for it.
'id' Field Ignored in Typesense v0.22.1
Nader reported an issue with the `id` field in Typesense v0.22.1. Kishore Nallan clarified it was a change in the version, directing to the corresponding document.
Populating `id_search` Field in Typesense Firestore Extension
Vera asked for guidance on automatically populating a custom field in a Typesense Firestore extension. Jason advised creating a new field from the application when creating the Firestore document and then sync that field into Typesense.