Manticore Search 28.5.0 lets RT tables use UUID as native document ID

Prior to version 28.5.0, Manticore Search only supported unsigned 64-bit integers as document IDs, forcing developers to maintain a separate mapping between UUIDs from primary databases and numeric Manticore IDs. This created reliability risks during updates and deletions, since a missing or outdated mapping could cause changes to target the wrong document or fail silently. Manticore Search 28.5.0 introduces native UUID support for RT tables, allowing the same UUID to serve as the document ID across the primary database, message queues, logs, and the search index. Operations such as INSERT, UPDATE, REPLACE, and DELETE can now reference the UUID string directly, eliminating conversion logic and the signed/unsigned integer overflow issues present with numeric IDs. UUID identifiers require no central registry, enabling parallel or offline ID generation, though uniqueness still depends on the correctness of the chosen UUID generator.