Atlas Search
149 results found
-
Make the size bigger of Query search results
Hey, recently I saw that in find section, where all data shown, is bit smaller in view point. I mean we can't see properly entire obj. Right now we have only less screen to see it.
Here I have attached two picture of find section. Plz make the screen bigger to see more...
Hope to implement my ideas.....1 vote -
Support document-level RBAC for search query results
Users of Elastic may configure role-based security for specific indexed fields or indexed documents. For document-level security, a query filter(s) is associated with a role, and an authenticated search query provides the role. The search engine looks up RBAC rules for the given role and index combination, adds the filter or filters defined for the role and adds the filters as part of a compound search query. This allows an easy form of document-level RBAC so certain roles may search and access only a given set of documents based on one or more filter query fragments.
https://www.elastic.co/guide/en/elasticsearch/reference/current/document-level-security.html
1 vote -
Configure Search Relevance or Results Ordering in the UI
I want to be able to configure search relevance or the order of results with a n Atlas UI module and no code.
2 votes -
Automatically recreate Atlas Search indexes on a collection after the collection is dropped and recreated or overwritten
Currently, if you use the $out aggregation stage to modify a collection with an Atlas Search index, you must delete and re-create the search index. Also, if another collection is renamed with dropTarget:true to an existing collection that already has Atlas Search indexes on it, then it is necessary to recreate the Atlas Search indexes after the collection rename completes (which involves dropping the original collection).
This is a feature request to automatically recreate the pre-existing Atlas Search indexes on a collection after that collection is dropped and recreated (using either $out or renameCollection).
8 votes -
Atlas search to provide the ability to query number (long/double) fields
When querying mongo using atlas search, today it requires that the query parameter be a string. Ideally, I would like to be able to also search using numbers. Our stakeholders want the ability to type into a dropdown select field , type a number, and have it pull back a list of data.
Today, we are using atlas search to query against a multiple set of fields, and pull back the most relevant results. It would be nice to include number fields as part of our index in order to allow those same stakeholder the ability to query by the…
15 votesAdmin mistake! Long Numbers are also still unavailable. Reopening this and I am sorry for the confusion.
-
Enable Atlas FTS to index an Atlas cluster logs
Atlas already provides the ability to create FTS index on the collection data, but retrieving and searching on the mongod log files information is pretty bad. Customers have to download the log files, then store them, parse and index on some other tool, that typically offers FTS capabilities. Why not just cut the time it take customers to perform all of those tasks and create that ability within Atlas itself?
1 vote -
Percolator for Atlas search to support Reverse look ups
Percolator for Atlas search to support Reverse look ups for real estate property data
4 votes -
Version + Feature Availability Matrix
As a customer, I would like to know what features work with which versions of MongoDB and Atlas Search.
Does facets work with 4.2, or 4.4, or version 5 for instance.
1 vote -
Did you mean? Spell Checker
I'd like a spelling check feature that will handle cases where the user misspells a word and still match what the user probably intended.
1 vote -
Allow to create Atlas Search index on a not existing collection
Currently it is not possible to create an Atlas Search index on a not existing collection, this makes more complicated to automatise the index creation on new clusters (e.g. via terraform).
Would be nice to allow the implicit collection creation when creating an Atlas Search Index.
5 votes -
Percolator/reverse search
Ability to store queries that allow you to supply a document and return the queries that match it.
5 votes -
RBAC for Atlas Search
Atlas Search Indexes can only be managed via MongoDB credentials (Terraform or API calls), with required role "Project Data Access Admin" (see https://docs.atlas.mongodb.com/reference/api/fts-indexes-create-one/#required-roles ). It would be great if we could create/delete search indexes using database credentials, similarly to regular indexes.
Because of that constraint, we need to provision dedicated apikey for our application ; in order to create the relevant search indexes. However, providing "Project Data Access Admin" is too much of a security risk - considering the power of such role.
Would it be possible to have dedicated "Atlas Search Admin" role which would allow creation / updating…
3 votes -
Query_syntax operator should support lucene syntax
At the moment the query_syntax seems to have a custom syntax. It looks similar to lucene syntax but is not the same.
There are a few differences to azure and elastic and I don’t understand whether I am doing something wrong or not.
What all three service have in common is that they are built on top of lucene, therefore I though that the querystring operator uses the lucene query syntax as it seems to be done by elastic and azure: https://lucene.apache.org/core/29_4/queryparsersyntax.html
Documentation about the elastic query string query can be found under: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html
There are a few…
2 votes -
Allow the option to mention the number of search results needed
I would like to get only the top scored 1000 or 2000 records while doing the search. Currently this is 2 step process : $search and then use the $limit stage.
4 votes -
Total Document count on Filter
It's a very small feature but very useful with respect to use case, whenever someone filters on Atlas nowhere it shows the total number of result we got, till we didn't reach the last page so it's very useful if we can see the total number of records at least after filtering or it will be great if it is visible on each page.
4 votes -
wildcard path support for range operator
Currently wildcard path can be constructed to 4 operator(text, phrase, wildcard and regex). Some use cases will be there to use the wildcard path for numeric which can be used by range operator
{ a : { "6578ghg" : { value : "not 55" } } }
{ a : { "9578uhg" : { value : 55 } } }Above 2 document if we have dynamic mapping of search index and below query cannot be used as range does not support wildcard in path:
db.dates.aggregate([ { $search :{ index:"synonyms", compound:{filter:[{text:{query:"55",path:{wildcard:"metadata.*.value"}}},{range:{gte:55,lte:55,path:{wildcard:"metadata.*.value"}}}]}}}])
Is there any plans/restriction for adding wildcard path support…
3 votes -
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 -
Improve error message when index definition exceeds 3KB
hen you create an index definition on the free plan that exceeds 3KB you get the following message:
{"detail":"A tenant FTS index may not exceed 3 KB in size.","error":400,"errorCode":"TENANTFTSINDEXTOOLARGE","parameters":[],"reason":"Bad Request"}
The message could be clearer. I had no idea what it meant and had to search the docs for that.
The limitations are described here: https://docs.atlas.mongodb.com/reference/atlas-search/limitations/
1 vote -
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 see your idea?