Atlas Search
148 results found
-
Make it easier to manage stop words
Right now, managing stop words is a very manual process.
1 vote -
Site Search
Provide tools to easily add Atlas Search to index and search our website.
1 vote -
Easier Ranking
It is difficult to rank search results just using scores. There should be better tools for managing rankings.
1 vote -
Search Personalization
Customize search results based on user profiles or other behaviors
1 vote -
Autocomplete User input Query Suggestions
We are using the autocomplete index type, but we would like it to be able to record new suggestions based on user input.
1 vote -
Search Page User Interface
We would like to have a search page that automatically hooks up our Atlas Search indexes to our application.
2 votes -
Support Partial Indexing
We have a large collection but would only like to index the most recent entries, which would reduce the amount of space and resources it would take to index and query.
42 votes -
Run aggregation pipelines on dedicated resources
When dealing with large collections(my usecase is 2billion+) it would make sense to run these aggregation's on dedicated resources like Azure Functions(my guess is that currently the aggregation pipelines are run(and somehow throttled) on the same resources as the cluster runs.
Not sure how much are the aggregations internally tied to how the data is stored(maybe they are somehow taking advantage of that) but if its straight up pipe with filters and aggregations on top of it, this would be a huge step to allow using Mongo as Big Data Platform, since it would allow reasonable scaling of the pipeline…
1 vote -
Allow $search to be a later stage in the aggregation pipeline
Currently $search is required to be the first stage in the aggregation pipeline. It would be more intuitive if we could use after other operators, such as $match.
81 votes -
Errors When Querying Non-existent Indexes
I renamed the first index I created when testing out the feature so it wasn't default, and spent quite a bit of time debugging why my queries were returning no documents. As it turns out it the default index that it queries if not defined is "default", but that index didn't exist. Instead of throwing an error about querying a non-existent index, it just returned an empty array which was very frustrating
9 votesThis work is under review and research.
-
toggle or autohide left side menu and upper menu while
add a toggle button to minimize the width of menus taking the larger part of the screen while working with a specific cluster.
2 votes -
New Analyzers
Customer is asking about adding new Analyzers language for Polish , Slovenian, Slovak and Croatian .
5 votesWe have planned to add more analyzers.
-
1 vote
-
Support additional highlighting options
Right now Atlas Search highlighting only supports text in the sentence surrounding a match, ignoring any other sentences in a field that have also been indexed.
I would like to be able to change the default behavior to meet my needs.
4 votes -
Support Full Text Search in Stitch SDK
Allow for the use of the $searchBeta operator in all SDKs
1 vote -
More useful query error
When you enter a query, if there is any kind of syntax error, you get dumped to a page where your only option is to return to clusters. Then you need to renavigate to your db and collection to attempt a new query.
This is really frustrating as instead of just being able to go back and correct your mistake, you must start writing the query again from scratch.
Why not put users back where they were and restore the query they were attempting so it can be easily fixed? Or better yet, check the query before you try to…
1 vote -
Disable alerts during search index builds
We're building a full-text search index, and I guess that causes high CPU usage on the cluster. So I've been getting alerts pretty much every few minutes for about 16 hours. I went to "acknowledge" the alert, but since it's flapping, the acknowledgement gets removed when the CPU recovers, and then a new alert is generated a few minutes later.
I would like to be able to disable alerts during search index builds so that I am not spammed with emails.
0 votes -
import index definitions from SOLR or ElasticSearch
I don't want to have to write my index definition over again. Is there a way I can import or transform it so that my existing definition can just work?
1 vote -
Allow search users to bring their own encryption key
I want to use my own encryption key so I know that my search data is encrypted with credentials I manage myself
4 votes -
API to know if FTS is enabled on a collection
As of now I can't find a way to detect whether a collection has FTS enabled or not. Indexes are not shown on the indexes() API. In a multi environment context, we usually want to implement a fallback implementation using another text search option when FTS is not available (dev or staging env for instance).
By not having an API to know if it's available or not, you can throw $searchBeta functions in a pipeline on cluster without FTS. It won't fail but you'll get no results. You cannot differentiate that from a true empty result set.
0 votes
- Don't see your idea?