Querying & Aggregations

Showing 47

support parallel query executions include find(), aggregation()

To use multi-core environment and enhance the query performance w/ a large amount of documents, need a parallel execution. Sharding or microsharding is not an alternative in this case.

Guest almost 2 years ago in Querying & Aggregations 0 Submitted

3 VOTE

define the random seed manually, for $rand and $sample

It will be great if an additional paramater to define the seed for $rand and $sample could be use.

Guest about 2 years ago in Querying & Aggregations 1 Submitted

2 VOTE

Make $merge support DELETE operation

Currently, the `$merge` only supports insert/update/upsert/merge behaviour. It would be great to support delete behaviour. A common use case would be in-place document deduplication/clean-up in a collection.

Guest over 1 year ago in Querying & Aggregations 0 Submitted

3 VOTE

$merge

Report number of docs matched, merged, skipped, etc. from a $merge stage. Alternatively, return the merged doc results as a pipeline result to pass to additional stages.

Guest over 2 years ago in Querying & Aggregations 0 Submitted

3 VOTE

Document scoped RBAC - Permission for collection document fields

Roles and accesses can be defined on the basis of collections that define roles for users. It would be nice if these access permissions could be made within the scope of the fields under the collection and the query results would be returned accor...

Guest almost 3 years ago in Querying & Aggregations 1 Submitted

1 VOTE

Is there any limitation on size of query in pipeline (character in query, not data)

I have an aggregate query, when the character in pipeline over 21066 character, the result return wrong format that the pipeline expected. So I wonder is there any limitation on size of query in pipeline? My case is: Query: [ "$match":{"profileI...

Guest about 1 year ago in Querying & Aggregations 0 Submitted

1 VOTE

Support concise correlated queries for $graphLookUp

Similar to $lookUp, support concise correlated queries for $graphLookUp. It would allow adding a $project stage to reduce overhead.

Guest about 1 year ago in Querying & Aggregations 0 Submitted

3 VOTE

Support expressions in $densify range bounds

The $densify aggregation pipeline stage seems unable to evaluate range bounds expressions, requiring the range bounds to be constant. See the following example (the collection testcoll contains a single documents with only the _id field): ``` s...

Guest over 3 years ago in Querying & Aggregations 3 Submitted

2 VOTE

Flatten arrays in group stage

Have group operators to flatten document arrays into a single one with or without repeated elements. So -> doc1 = {arr: [1,2,3,4], gr: "group"}, doc2 = {arr: [5, 6, 7, 8], gr: "group"} {$group: {_id: "$gr", arrays: {$***: "$arr"} } } => {_id...

Guest over 2 years ago in Querying & Aggregations 1 Submitted

1 VOTE

$sort should allow 0 as argument meaning "no sort"

The $sort operator and aggregation stage should allow 0 (possibly also null) as an argument for the field sort order, meaning, "Don't sort." This allows a variable to be passed in that can conditionally skip the sort operation, in addition to the ...

Guest about 1 year ago in Querying & Aggregations 0 Submitted

Please enter your email address

FILTER BY CATEGORY