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.
Nov 27, 2021 (26 months ago)
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?
Kishore Nallan03:15 PM
2. Do you mean the "out_of" field in response?
Kishore Nallan03:31 PM
Indexed 3011 threads (79% resolved)
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.
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.
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.