Atlas Search
158 results found
-
Implement basic aritmetic operations for the Decimal128 datatype
Feature Request:
Implement basic aritmetic operations (e.g. addition) for the Decimal128 datatype.Context:
I am working with high precision floats in Python and I am storing my data in MongoDB. When I get a high precision float out of MongoDb, I then need to convert it to the native Python decimal datatype before I can do basic arithmetic like addition. It would be great if your Decimal128 datatype supported the same mathematical operations as Python's decmial datatype. I documented this issue and provided sample code to work around the limitations here:https://github.com/NadimGhaznavi/kb/wiki/Handling-Floating-Point-Math-with-Python-and-MongoDb
Love your product, keep up the awesome work!!!…
1 vote -
Implement basic aritmetic operations for the Decimal128 datatype
Feature Request:
Implement basic aritmetic operations (e.g. addition) for the Decimal128 datatype.Context:
I am working with high precision floats in Python and I am storing my data in MongoDB. When I get a high precision float out of MongoDb, I then need to convert it to the native Python decimal datatype before I can do basic arithmetic like addition. It would be great if your Decimal128 datatype supported the same mathematical operations as Python's decmial datatype. I documented this issue and provided sample code to work around the limitations here:https://github.com/NadimGhaznavi/kb/wiki/Handling-Floating-Point-Math-with-Python-and-MongoDb
Love your product, keep up the awesome work!!!…
1 vote -
Allow to configure/adjust the number of nodes within a regions in a multi-region Atlas search cluster
Today, i enabled an isolated search node cluster with 2 nodes for one of our cluster which is an multi-region cluster with 4 nodes in N.Virginia and 1 node in Oregon. I can see that search node cluster has added 2 nodes in N.Virginia and 2 nodes in Oregon.
We use N.Virginia as our primary region and Oregon as our secondary region mainly considering it (Oregon) only for Disaster recovery purposes, so having 2 search nodes in Oregon will not be of much use for us, and I don't see an option in the mongoDB Atlas console to configure the…1 vote -
Atlas Search for time series collections
It would be nice if we could use atlas search on a time series collection
1 vote -
Atlas Search equivalent for "should" but ignoring score
Currently to perform an "OR" check in an Atlas Search query the only available operator is "should" which contributes to score.
I propose "ought" the equivalent operator, but doesn't contribute to score.
Alternatively, I suggest an option to $search to omit score entirely, this could offer a little performance boost on large document set by removing the need to track score when it is not needed.
1 vote -
allow atlas search for serverless instances
As of now, atlas search is not allowed for serverless instances, but many people using serverless instances and they atlas search to perform some advanced search queries.
1 vote -
Atlas search Index is not updating.
Each time I perform CRUD operations in my collection, the Search Index doesn't update immediately. Instead, it takes a considerable amount of time. This issue significantly hampers the progress of my project. Any suggestions for improvement would be greatly appreciated.
1 vote -
1 vote
-
Atlas can be configured to raise alert notification when the Atlas cluster already scales to the max tier.
Atlas can be configured to raise alert notification only when the Atlas cluster already scales up to the max tier allowed. This can be help to avoid notification spams which does not require operation team actions and focus on the critical resource consumption alerts like cpu, memory, disk IO.
1 vote -
Synonyms support for autocomplete operator
Hi.
Having synonyms support for the autocomplete operator would be great! Is this possible?
Best regards,
Tim1 vote -
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 -
Ability to randomize score
I would like to be able to add randomness to the search results' score.
1 vote -
Ability to exclude documents matching a certain criteria from index
We don't do physical deletion of documents, but a logical one, flagging them by setting a value for a
deleted_atfield.We would like an option to exclude documents where that field exists and is not null from the index, because they will never be returned and are only consuming space of the index.
Currently we use a
mustNotcondition to exclude them, but of course they are still being indexed.The ideal would be to be able to define the exclusion criteria in the index definition.
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
- Don't see your idea?