Manticore Search 28.5.0 introduces native UUID support as the document ID type for RT tables, eliminating the need to maintain a mapping between UUIDs from a primary database and numeric IDs in Manticore. Previously, document IDs were unsigned 64-bit integers, forcing developers to store UUIDs as separate attributes and maintain ID mapping tables. Now, a UUID can be declared as the `id` type at table creation, used directly in INSERT, UPDATE, REPLACE, and DELETE operations, and either provided by the application or auto-generated by Manticore as UUIDv8. Limitations include: UUID IDs only work in RT tables (not plain, percolate, or shard tables), range comparisons on UUID IDs are unsupported, existing tables cannot be migrated from numeric to UUID IDs, and the value 0 no longer triggers auto-generation.

7m read timeFrom manticoresearch.com
Post cover image
Table of contents
Why a second ID is a problemWhat a UUID isWhat changed in Manticore 28.5.0Who creates the UUIDWhere it worksSummary
15.5K Impressions