Feedback

the profile output in association with the $comment query operator need to have consistency across operations.

I have observed the different profile result with regard to $comment query operator in association with find and update operation respectively as follows; - find operation shows a comment on the command.filter.$comment and the command.comment fie...

Guest over 4 years ago in Querying & Aggregations 0 Submitted

1 VOTE

multiple centersphere as a geometry for geowithin

im looking at one of my queries that a system regularly runs and some times we look for records that are within up to 250 different centerspheres, i wornder if we could enable, like geowithin has the ability to support multiple poligons, we could ...

Guest over 4 years ago in Querying & Aggregations 0 Submitted

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":"TENANT_FTS_INDEX_TOO_LARGE","parameters":[],"reason":"Bad Req...

Guest over 4 years ago in Atlas Search 0 Submitted

1 VOTE

$populate stage

Please provide a $populate stage that allows to resolve single referenced documents. Internally it could use the combination of $lookup and $unwind: https://stackoverflow.com/questions/41482559/how-to-return-single-object-instead-of-array-in-look...

Guest over 4 years ago in Querying & Aggregations 0 Submitted

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...

Guest over 4 years ago in Atlas Search 0 Submitted

1 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 degra...

Guest over 4 years ago in Atlas Search 0 Submitted

1 VOTE

Provide straightforward syntax for 1-to-1 joins in aggregation

The syntax for joins that bring back multiple documents from foreign collections is very straightforward and yields exactly what one would expect, but simple joins that are bread and butter in SQL require very convoluted and expensive to run synta...

Guest over 4 years ago in Querying & Aggregations 4 Submitted

1 VOTE

Display warning when loading an index definition with the Visual Editor that contains unsupported features

The Visual Editor does not currently support custom analyzer definitions or synonym mappings -- those have to be defined in the JSON Editor only for now. If an index definition that contains such unsupported feature is loaded into the Visual Edito...

Roy Kiesler almost 5 years ago in Atlas Search 0 Submitted

1 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 ...

Guest almost 5 years ago in Atlas Search 0 Submitted

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.

Guest almost 5 years ago in Atlas Search 0 Submitted

Please enter your email address

FILTER BY CATEGORY