#community-help

Customizing Object IDs and Server Responses

TLDR Daniel had queries about altering default object ID generation and restricting server response. Kishore Nallan clarified that default ID changes aren't supported but acknowledged a future provision to customize server responses.

26mo

Join the chat

Nov 27, 2021 (26 months ago)

Photo of md5-3e862430ae06b87120e3640d3f9f8061

Daniel

03:12 PM

Two questions:

1-Can we change the way the default ID for every object is generated? Instead of Serial, an UUID and more.

2-Can we prevent the server from responding with how many hits were found?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

03:15 PM

1. No way to make it a UUID. If you want you can explicitly send an UUID as the "id" field of the document sent.

2. Do you mean the "out_of" field in response?

Daniel

03:26 PM

1-No yeah, it's because I don't want to use serialized ids, but it's fine for now.

2-Exactly, the out_of field

Kishore Nallan

03:31 PM

Its not possible to remove that. We are thinking of making it part of exclude fields which can be added as part of scoped API key so that it will always be respected.

Typesense

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

Indexed 3011 threads (79% resolved)

Join Our Community

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.

21mo

Discussions on Typesense, Collections, and Dynamic Fields

Tugay shares plans to use Typesense for their SaaS platform and asks about collection sizes and sharding. Jason clarifies Typesense's capabilities and shares a beta feature. They discuss using unique collections per customer and new improvements. Kishore Nallan and Gabe comment on threading and data protection respectively.

35mo

Handling Kinesis Stream Event Batching with Typesense

Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.

24mo