MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Completed
Categories Atlas Search
Created by Guest
Created on Sep 1, 2020

RELATED FEEDBACK

Add support for UUID datatypes in Atlas Search

Currently, UUID is not one of the supported datatypes for Atlas Search. This is a feature request to add support for UUID datatypes in Atlas Search.
  • ADMIN RESPONSE
    Oct 18, 2025
    This work is now complete. Update your search index ( https://www.mongodb.com/docs/atlas/atlas-search/rebuild-index/ ) to: 1. Index fields using the uuid field mapping type ( https://www.mongodb.com/docs/atlas/atlas-search/field-types/uuid-type/ ) 2. Query using the equals ( https://www.mongodb.com/docs/atlas/atlas-search/equals/ ) or in ( https://www.mongodb.com/docs/atlas/atlas-search/in/ ) operators 3. You can also sort ( https://www.mongodb.com/docs/atlas/atlas-search/sort/#std-label-sort-ref ) on UUID fields
  • Guest
    Feb 22, 2024
    any updates on this?
    Reply
  • Guest
    Dec 1, 2023
    We also use UUID, as a GUID representation, and would like to use the Atlas search on filtered records by UUID collection. However, according to https://www.mongodb.com/community/forums/t/search-index-filtering/195825, we should include UUID in the search index. P.S. We have more than 10M records, so without filter, or with post-filter search is quering so long...
    Reply
  • Guest
    Feb 28, 2023
    I use UUIDs across various services and databases and for supporting public API interactions. The implementation independence from Mongo and commoness in web apps makes them a valuable identifer tool and therefore I feel they should be supported within Mongos indexing capabilities. I mean, if you can index a date object but not a UUID binary, then like .. wut? It would be great to be able to track the progression of it, such as when we can expect to see it supported.. are we talking mongths or longer?
    Reply
  • Guest
    Aug 17, 2022
    Thank you @Erich! For anyone who needs, here is a trigger to add the string version of UUID: exports = async function (changeEvent) { const doc = changeEvent.fullDocument; const id = changeEvent.documentKey._id; const searchId = id.toHex().replace(/^(.{8})(.{4})(.{4})(.{4})(.{12})$/, '$1-$2-$3-$4-$5'); const collection = ...; collection .updateOne( { _id: id }, { $set: { 'searchId': searchId } } ); }
    Reply
  • Guest
    Aug 16, 2022
    @Daniel, the only workaround I've found is to store a string version of the UUID and index that in your search index until this is supported. I wish this would get more focus as it's a real issue for my clients.
    Reply
  • Guest
    Aug 15, 2022
    Is there any workaround?
    Reply
  • Guest
    Jan 31, 2022
    What is the status of this? If this is being tracked, can someone link this to jira ticket please :)
    Reply