There is $facet
aggregation stage in mongo since 3.4 -
It's cool. It allows to processes multiple aggregation pipelines within a single stage on the same set of input documents.
But it doesn't allow to use one $facet inside another. Cite: "Any other aggregation stages can also be used with $facet except: $facet, $out, $geoNear, $indexStats, $collStats"
Does anyone understand the reason?
I just want to use $facet this way:
db.collection.aggregate([{
$facet: {
'first': [
$facet: { // here is the sub $facet
'subFirst1': [],
'subFirst2': []
}
],
'second': [
//...
]
}
}])
This should produce a doc like:
{
first: {
subFirst1: {...},
subFirst2: {...}
},
second: {...}
}
If I try this it throws the error:
specified stage is not allowed to be used within a $facet stage: 0: { $facet: { subFirst1: [ ... ] } }"
Facets can be nested to multiple levels deep and each child facet can be defined with faceting options.
The $facet stage allows you to create multi-faceted aggregations which characterize data across multiple dimensions, or facets, within a single aggregation stage. Multi-faceted aggregations provide multiple filters and categorizations to guide data browsing and analysis.
The pipeline method provides efficient data aggregation using other operations present in MongoDB. It can also operate on a sharded collection. It can also use MongoDB indexes to improve its efficiency at some stages.
Definition. $project. Passes along the documents with the requested fields to the next stage in the pipeline. The specified fields can be existing fields from the input documents or newly computed fields.
It's not only about facets. In general it's not allowed to create subfields in an aggregation stage. For example the following attempt of creating a complex value fails.
$addField: {
a.b: "foo"
}
And that makes quite sense, since a value can be a primitive type, a complex object or an array. Don't know if that is a satisfying answer to you, maybe it's a little consolation that this not only counts for facets, but for all assignments in general.
I want also say that your intention is plausible. Especially in a database system, where no schema is required and each document can differ from others, it would be nice to have that feature. If you actually manipulate data you can do so with set
. But on your intermediate results, you are not allowed to perform that action. One can perceive that as a bit inconsistent.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With