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 Will Not Implement
Categories Atlas Search
Created by Guest
Created on Jan 4, 2021

RELATED FEEDBACK

Allow autocomplete search on multiple fields using a wildcard path or by specifying multiple fields in the path

Currently, (unlike the text operator) the autocomplete operator does not accept a path which is an array of field names. Also, a wildcard path ("path": {"wildcard": "*"}) cannot be specified for an autocomplete query. Therefore, the only way to perform an autocomplete search on multiple fields is by using the compound operator. This is a feature request to allow autocomplete search on multiple fields by using a wildcard path or by accepting an array of multiple fields in the path.
  • ADMIN RESPONSE
    Oct 18, 2025
    This functionality can be achieved with the *compound* ( https://www.mongodb.com/docs/atlas/atlas-search/compound/ ) operator. For an example of searching multiple fields with the autocomplete operator, see the Advanced Example in this ( https://www.mongodb.com/docs/atlas/atlas-search/tutorial/autocomplete-tutorial/#run-an-autocomplete-query ) tutorial ( https://www.mongodb.com/docs/atlas/atlas-search/tutorial/autocomplete-tutorial/#run-an-autocomplete-query ). Please let us know if you have any questions or additional feedback about this solution.
  • Guest
    Jul 12, 2023
    As mentioned by Daniele, you can achieve this by using the compound operator, see example here: https://www.mongodb.com/docs/atlas/atlas-search/autocomplete/#search-across-multiple-fields
    Reply
  • Guest
    Jan 24, 2023
    is this issue cleared? I am still unable to pass the array of fields.
    Reply
  • Guest
    Sep 5, 2022
    still waiting for the solution
    Reply
  • Guest
    Jul 18, 2022
    Could we maybe get a little bit of visibility on that? Are we looking at a few weeks? a few months? one more year? Any vague info would help us out there planning our developments. Thanks.
    Reply
  • Guest
    Jun 14, 2022
    Hi there. Could we at least get an update as it is nearly a year since work was going to begin on this. Thanks in advance.
    Reply
  • Guest
    Mar 4, 2022
    Any update on that? It's still quite blocking not to be able to do a simple autocomplete search on an array of objects. Thanks, please keep us posted.
    Reply
  • Guest
    Feb 7, 2022
    Also would love this. I can work around for now, but would be a nice feature. Any updates? Would also be great if this limitation could be mentioned in the docs. If it is already, I didn't see it. Thanks.
    Reply
  • Guest
    Feb 1, 2022
    Any update on this issue? I see the last comment was about 6 months ago. Running into this one now.
    Reply
  • Guest
    Nov 24, 2021
    I ran a test that worked: { "mappings": { "dynamic": false, "fields": { "category": { "foldDiacritics": true, "maxGrams": 15, "minGrams": 2, "tokenization": "nGram", "type": "autocomplete" }, "wisdom": { "foldDiacritics": true, "maxGrams": 15, "minGrams": 2, "tokenization": "nGram", "type": "autocomplete" } } } } Search with: db.examplecoll.aggregate([ { $search: { "compound": { "should": [ { "autocomplete": { "query": "conn sur", "path": "category" } }, { "autocomplete": { "query": "conn sur", "path": "wisdom" } }], "minimumShouldMatch": 1 } } } ])
    Reply
  • Guest
    Nov 24, 2021
    This feature will be useful. We have lot of use case for multiple fields and partial search with case insensitive.
    Reply