SERVER-22760 Sharded aggregation pipelines which involve taking a simple union should merge on mongos

1 files changed, 2 insertions, 2 deletions

diff --git a/src/mongo/db/pipeline/document_source_facet.cpp b/src/mongo/db/pipeline/document_source_facet.cpp
index aba1f5f115c..e553ea2fa62 100644
--- a/src/mongo/db/pipeline/document_source_facet.cpp
+++ b/src/mongo/db/pipeline/document_source_facet.cpp
@@ -243,12 +243,12 @@ DocumentSource::StageConstraints DocumentSourceFacet::constraints() const {
 
     for (auto&& facet : _facets) {
         for (auto&& nestedStage : facet.pipeline->getSources()) {
-            if (nestedStage->constraints().mustRunOnPrimaryShardIfSharded) {
+            if (nestedStage->constraints().hostRequirement == HostTypeRequirement::kPrimaryShard) {
                 // Currently we don't split $facet to have a merger part and a shards part (see
                 // SERVER-24154). This means that if any stage in any of the $facet pipelines
                 // requires the primary shard, then the entire $facet must happen on the merger, and
                 // the merger must be the primary shard.
-                constraints.mustRunOnPrimaryShardIfSharded = true;
+                constraints.hostRequirement = HostTypeRequirement::kPrimaryShard;
             }
         }
     }