Atlas Search
166 results found
-
Add other operators (range/TO, NOT) in queryString
I like lucene query string syntax (https://lucene.apache.org/core/8_10_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package.description). I think it is more human-readable. So, please add the range operator to it and if it's possible, add other ones like NOT, regex, boosting, proximity and fuzzy.
If it's hard, please focus on range and NOT1 vote -
Enhanced alerting for Atlas Search
I am looking to set up alerts for the following criteria related to Atlas Search:
- Alert and metrics based on search index queue size (when we expect results to be slow to appear)
- Alert when a search index is being rebuilt (when we expect degraded performance and potential downtime) - there are already alerts included by default for Search Index Build Complete, and Search Index Build Failed, could it just be a new alert for Started?Thanks
1 vote -
Don't require path on search queries
It would be nice if a path defaults to all paths in the index. For example, imagine I have a customers collections with the fields "firstName" and "lastName" and I want to create a search based on user's full name. Then I create a search index on these two fields. Now imagine I call this index "fullNameSearch". Then whenever the "fullNameSearch" index is used, I want to run it on all paths. Instead of me having to specify the paths, it would be nice if the path defaults to all fields used in the index.
Another example where this would…
1 vote -
profiler search by db
Currently, the profiler search is for namespace.collection_name. If I would like to see how all collections for a given namespace or DB are behaving it's a very tedious task and not user friendly at all.
1 vote -
Leverage atlas search indexes in find and count operations
Currently the documentation wasn't outright clear that Atlas search indexes can only be leveraged through Aggregation operation. It will be great if we can leverage them in find and count operations as well.
1 vote -
Please add lucene.kuromoji
I just happened to know that full-text search feature is available in MongoDB Atlas. Greatly appreciated if lucene.kuromoji is added to a list of language-specific analyzers. Currently, there is only a generic Chinese, Japanese, and Korean analyzer.
1 vote -
Ability to search for a cluster
As an enterprise we have many projects with many clusters in each project. Our naming convention isn't always standard so it would be helpful to be able to search for a cluster based on part of the cluster name and have the search result tell me in which project the cluster exists.
1 vote -
1 vote
-
Allow searching of images
We have scanned images with text, and would like to have OCR capabilities so that we can search against those images
1 vote -
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 -
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 -
1 vote
-
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 -
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 -
Support basic recommendations
In Elastic we leverage basic built-ins like "more like this" so we don't show zero results sometimes and also as a simple recommendation engine in cases we don't use our own custom recommendation logic
https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-mlt-query.html
1 vote
- Don't see your idea?