Atlas Search
148 results found
-
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 -
Add Atlas Search metrics into integration with Datadog
Problem Statement,
Atlas Search metrics (https://docs.atlas.mongodb.com/view-atlas-search-metrics#atlas-search) are not sent to Datadog (Datadog's MongoDB Atlas integration (https://docs.datadoghq.com/integrations/mongodb_atlas/)).Proposal,
Add Atlas Search metrics to Datadog integration (start sending Atlas Search metrics from Atlas to Datadog).4 votes -
Allow queries with $search to be covered by the Lucene indexes without loading from disk in Mongo
If the fields to be filtered on or projected on are all in the Lucene index, it would give the best latency to be able to return the data from the Lucene index only, and not have to separately look that data up from the Mongod
4 votes -
API to list all Atlas Search Indexes configured across all collections in the cluster
Currently, there is an API to list all Atlas Search indexes configured for a specific collection. However, there is no API that lists all Atlas Search indexes configured across all collections across all databases, in a particular cluster. The Atlas UI shows this, but the Atlas API does not have that functionality.
This is a feature request to add the API capability to list all Atlas Search indexes configured on all collections in a cluster.
2 votes -
Autocomplete with `fuzzy` scores all results as `1`
Using autocomplete with the
fuzzyoperator returns results, but they are scored all with the same value (1). This has been reported a couple times in the developer forum as well:https://developer.mongodb.com/community/forums/t/fuzzy-autocomplete-score/13341/4
This can make it difficult to process and rank results on the client side, especially for high volumes of returned documents. It would be helpful if autocomplete + fuzzy would support relative scoring.
3 votes -
Allow ability to exclude specific fields from Atlas Search
In order to reduce index size and improve performance, we should be able to exclude specific fields from the Atlas Search index.
2 votes -
Analzye Endpoint or Analysis Screen
Please show how an index is analyzed based on a given index definition.
10 votes -
Support Decimal128
Enable indexing and querying of near and range operators for Decimal128.
18 votes -
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 -
2 votes
-
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 -
Add truncate collection button, delete documents older than...
In the old interface we can truncate collections without using additional software, just using WEB GUI to keep small database size.
It would be nice to have the ability to delete older documents. This option is usable for IOT or medical implementations (Nightscout).2 votes -
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 -
Return results from within arrays
I have a document that looks like this:
{
shoppingList: [ { name: "red hat"}, { name: "green shoes"} ]
}I would like to query $search for "green" and return {name: "green shoes"} instead of returning the entire document.
11 votes -
Atlas Search for Online Archive
As a user of Online Archive, I would like full text search capabilities from Atlas Search available to me.
6 votes -
The equals operator should support date datatype
Currently, for querying on "date" datatypes, we can only use "range" or "near" operators. The "equals" operator supports querying only "boolean" and "objectId" values, and not date values.
If we want to do equality based matching for date datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases.
Therefore, this is a feature request for having equals operator support date datatype (in addition to boolean and objectId).
3 votes -
Save pipelines to run in aggregation mode
A Button to save pipeline in aggregation tab and run this saved pipelines.
7 votesDanilo – Great idea. We are reviewing it at the moment. Just curious whether you use the agg tab to do adhoc analysis or test queries which you eventually put in your app?
-
Official React Component for Atlas Search
One of the reasons Algolia got so popular might be the fact that they provided instantsearch.js. The library was really easy to get started and intuitive to understand.
I read the Atlas Search's great tutorial(1) and watched the video(2) and cloned the repo FTS_MovieSearch on GitHub. They are really insightful and helpful. Yet, if there is official React component which provides some of (not all) functionalities that instasearch.js offers, that would help Atlas Search to grow.
(I put "React" in title, but maybe vanilla JS/TS component would be better to consider)
I used to try setting up Atlas + Elastic…
4 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.
- Don't see your idea?