Querying & Aggregations

Showing 51 of 3954

Add setOnUpdate operator for Upsert operations

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 regularly want to upsert documents to mongo, and include a useful createdAt and updatedAt timestamp. createdAt is easy:...

WelcomeLend Operations 3 days ago in Querying & Aggregations 0 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 2 months ago in Querying & Aggregations 0 Future Consideration

1 VOTE

MongoDB missing support for GeoJSON-compliant indexing+intersection queries

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 are building a geospatial application that uses GeoJSON natively. We need to query MongoDB for a list of GeoJSON object...

Mitchell Horning 21 days ago in Querying & Aggregations 0 Submitted

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 5 months ago in Querying & Aggregations 0 Submitted

3 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 6 months ago in Querying & Aggregations 0 Submitted

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 almost 6 years ago in Querying & Aggregations 2 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 over 3 years ago in Querying & Aggregations 3 Submitted

1 VOTE

Allow descriptions for $expr sections in DB validation

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. Our collection has some complex $expr rules for validating our collection. Unfortunately, $expr does not allow us to add a...

Habibullah Aslam 3 months ago in Data Modeling & Indexing / Querying & Aggregations 1 Will Not Implement

9 VOTE

Handle Daylight Saving Time when $densify is used on a date field

When using "day" as "unit" for a $densify pipeline stage on a date field, the date is always advanced of 24 hours. This is however not always the expected result in timezones in which the year has one 23-hour and one 25-hour long day, because of D...

Guest about 3 years ago in Querying & Aggregations 1 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 almost 4 years ago in Querying & Aggregations 0 Submitted

Please enter your email address

FILTER BY CATEGORY