Atlas Search
166 results found
-
Additional function scores decay functions: exp & linear
Atlas Search currently only supports gaussian decay function for function scores. In 4 out of 5 of our use cases exp would be a much more natural choice.
Hopefully that is just a small task!
1 vote -
Ruby on Rails support of Atlas Search index management
Feedback from customer: "Currently we need to manage core DB indexes and atlas search indexes separately. We'd prefer to manage them all in the Rails model code but MongoID only supports core DB index configuration. We're having to use terraform for atlas search index management."
1 vote -
Token filter that removes duplicated entries
Create a token filter or a tokenizer or even an option that removes duplicate words in fields to avoid misleading scoring. For example: if I insert a document with a property "Testing testing document", another with "Testing example" and a third with "Testing foo" and I search for "Testing foo", the first document receives a higher score.1 vote -
knnBeta Limitations and Syntax
I tested the new knnBeta operator today and it worked so far.
Can we expect the current operator limitations to be gone by release?
The current limitations make it virtually impossible to use the knn operator as a replacement for previous text operators (like text).
I would prefer the filter parameter to be omitted and knn not have to be a top-level operator.1 vote -
wildcard paths in index specifications
It would make index specification easier in some cases if wildcards were possible in the paths. Yes we have dynamic indexing, but to keep the index size minimal and to be more flexible I want to index only the fields I really need. Consider the following example:
Example document:
{
foo: {
de: {
field1: 'bar',
field2: 'bar'
},
en: {
field1: 'bar',
field2: 'bar'
},
fr: {
field1: 'bar',
field2: 'bar'
},
}
}Index specification:
{
"mappings": {
"dynamic": false,
"fields": {
"foo": {
"type": "document",
"dynamic": false,
"fields": {
"$**": {
"type": "document",
"dynamic": false,
"fields": {…1 vote -
Multiple Capture Groups in RegEx Tokenizer
Currently the RegEx tokenizer only supports to either create a token from each match or for one capture group per match. This makes it impossible to reuse parts of the text for multiple tokens, for example when you want to tokenize "13.3" into "13" as well as "13.3" (our use case is searching products where we want to find a 13.3" device by searching for 13" as well as 13.3").
1 vote -
Duplicate search index
I want to be able to easily duplicate a search index in the Atlas UI.
1 vote -
search
Allow scoring of individual embeddedDocument searches or allow $unwind phase before $search to enable fuzzy searching for specific embeddedDocument in array of embedded documents
1 vote -
.NET Driver
It would be great if the .NET driver would support $search along with all the associated operators.
1 vote -
Support for OR Conditions
We need support for matching for one condition out of several. This is an important usecase for my requirements.
e.g. $or: [{ "airlines": "United" }, { "ticket_price": { $lte: 600.00 } }]
Thanks!
1 vote -
Provide features for array comparisons
It would be very helpful if we can lookup documents that have certain array fields that match the provided array in the query. Exact match, Any match etc should be supported. All data types should be supported.
e.g { text: { path: "city", query: ["New York", "Los Angeles", "Kansas"] } } should return all documents that have the city as ["New York", "Los Angeles", "Kansas"].
1 vote -
Filtered Indexes
Provide capability to create filtered indexes. This would allow creating tenant-specific indexes in a multi-tenant database.
While the current implementation does support this feature in a way, it requires manual maintenance of such indexes as there is an implicit assumption that each tenant would have the same fields.
Our core requirement is that each tenant can have their own set of fields. Filtered indexes would help reduce the size, hence requiring fewer system resources and possibly helping the database perform better.
1 vote -
Faster Search Index Builds
Today, my index build may take a long time (depending on the amount of documents being indexed) and I would like to see these be faster so I am able to develop and iterate faster.
Please comment current build time and preferred build time.
1 vote -
Display indexID in the UI
Just like the project ID is displayed on the Project Settings page, please display the index ID somewhere in the UI, so that we know what indexID to put when using the Atlas Search API endpoints (they require indexIDs but the UI displays only index names). That would make management and maintenance much simpler.
Unless I'm mistaken, the only way to know the indexID of an index I see in my UI is to make programmatic calls to some other API endpoints.
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 -
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
- Don't see your idea?