only bypass obsolete (and expensive) query

The rest of the flow is still needed to finish triggering completion events, until we refactor this more cleanly.
Vizzuality · Mar 7, 2024 · 70662ea · 70662ea
1 parent c81be11
commit 70662ea
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/api/apps/api/src/modules/scenarios-features/move-data-from-preparation.handler.ts b/api/apps/api/src/modules/scenarios-features/move-data-from-preparation.handler.ts
@@ -69,5 +69,12 @@ export class MoveDataFromPreparationHandler
         specificationId: command.specificationId,
       });
     });
+
+    this.eventBus.publish(
+      new DataMovedFormPreparationEvent(
+        command.scenarioId,
+        command.specificationId,
+      ),
+    );
   }
 }
diff --git a/...planning-units-features-aggregate/scenario-planning-units-features-aggregate-processor.ts b/...planning-units-features-aggregate/scenario-planning-units-features-aggregate-processor.ts
@@ -44,6 +44,13 @@ export class ScenarioPlanningUnitsFeaturesAggregateProcessor
   ) {}
 
   async process(job: Job<JobInput, true>): Promise<true> {
+    /**
+     * @debt Bypassing the original query, whose results are not needed anymore,
+     * and which was expensive to run. The flow that includes this processor
+     * should be cleaned up instead, to fully bypass
+     * ScenarioPlanningUnitsFeaturesAggregateProcessor.
+     */
+    return true;
     const scenarioId = job.data.scenarioId;
     await this.entityManager.query(query, [scenarioId]);
     return true;