Atlas Search
129 results found
-
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?