Skip to content

Tell us how to improve Atlas Search!

← Atlas Search

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.

76 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Harshad shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
started  ·  Marcus Eagan responded  · 

We’ve heard your feedback loud and clear. We are starting this work now.

Thanks for the feedback. We will update you when it is released very soon. Let us know if you have any questions. :-)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • vamsikrishna commented  ·   ·  Report

    is this issue cleared? I am still unable to pass the array of fields.

  • Guillaume commented  ·   ·  Report

    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.

  • Geoff commented  ·   ·  Report

    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.

  • Guillaume commented  ·   ·  Report

    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.

  • Joseph commented  ·   ·  Report

    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.

  • Luke commented  ·   ·  Report

    Any update on this issue? I see the last comment was about 6 months ago. Running into this one now.

  • Daniele commented  ·   ·  Report

    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
    }
    }
    }
    ])

  • Petchimutha commented  ·   ·  Report

    This feature will be useful. We have lot of use case for multiple fields and partial search with case insensitive.

Atlas Search

Categories

Feedback and Knowledge Base

(thinking…)