Querying & Aggregations

Allow specifying the output field of an $unwind

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. The $unwind stage overwrites the specified array path with a non-array value. This maps poorly with statically-typed progr...

Ivan Canet 13 days ago in Querying & Aggregations Submitted

13 VOTE

Please add support for auto-incrementing numeric IDs. For example, if an ID starts at 1000001, the next created record should automatically use 1000002

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. MongoDB lacks native support for auto-incrementing numeric IDs, forcing applications to use custom counter logic, which in...

Altaab Ansari 8 months ago in Performance & Optimization / Querying & Aggregations Future Consideration

1 VOTE

Granular Privilege for collMod Without Requiring atlasAdmin

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We execute the collMod command to apply or update collection validators as part of our deployment automation. Currently, t...

Somesh Saini 24 days ago in Querying & Aggregations Submitted

6 VOTE

Improve small collection lookup performance

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. Improved performance for lookups from large to small collections (where many origin documents match the same looked-up doc...

Ryan Peggs 11 months ago in Querying & Aggregations Future Consideration

35 VOTE

Allow configuration of 100mb memory limit per aggregation pipeline stage

In this old thread from 2016 (https://groups.google.com/forum/#!topic/mongodb-user/LCeFZZRz5EY) it was asked whether there was a way to increase the 100mb in memory limit of each stage of an aggregation pipeline. The responses centered around two ...

Guest over 6 years ago in Querying & Aggregations Submitted

21 VOTE

Add operator that would calculate distance between 2 geolocation points

It would be great to have operator that would calculate distance between 2 geolocation points, and not to do it manually with big aggregate queries. I suggest to add 2 new operators that would calculate distance in two different ways, as discuss...

Guest about 4 years ago in Querying & Aggregations Submitted

2 VOTE

Add Attribute Sorting/Reorganizing to get best index for $match in aggregation and other filters (by option)

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. I have found out that the order of attributes in my (different) $match stages are relevant to the query planner of what in...

Paul Coch 7 months ago in Querying & Aggregations Will Not Implement

4 VOTE

Allow Pinning Query Plan Cache Key to a Fixed Plan for a Given Query Shape Hash

Allow Pinning Query Plan Cache Key to a Fixed Plan for a Given Query Shape Hash n MongoDB 8.0, the new setQuerySettings command allows administrators to enforce index hints and other behavior based on the query shape hash. This gives users partia...

Vinicius Grippa about 1 year ago in Querying & Aggregations Submitted

4 VOTE

Implement a $hash operator for queries

Current State: MongoDB currently lacks a native $hash operator in the aggregation/query language. While certain helpers like convertShardKeyToHashed or $toHashedIndexKey exist, they are limited in scope: Not available as true query operators (e....

Guest about 1 year ago in Querying & Aggregations Submitted

11 VOTE

Raise the limit of 16 MB JSON between aggregation stages

When doing analytics, the 16 MB JSON limit between aggregation stages restricts the ability to process large amount of data. allowDiskUse does not help with all the various $operators and stages that we use. See ticket 00774514 for details.

Guest over 4 years ago in Querying & Aggregations Submitted

Please enter your email address

FILTER BY CATEGORY