[For MSFT Team Review]: Trigger compute size operation on dataset close
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test -
Documentation
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Anthos -
Azure -
GCP -
IBM
conventional commits spec?
Does this follow-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
This MR adds a trigger to re-compute the size of a dataset after it was closed.
As per the ADR, the trigger was added to the dataset PATCH
endpoint, in case dataset is being closed with or without an update to its metadata.
Computing the size of the dataset is an operation executed asynchronously in a separate component which will be added as part of a separate MR. The trigger creates a queue message and pushes into onto a Redis queue, where it can be picked up by the separate service.
How to test this MR?
- Run SDMS locally and register a new dataset.
- Close the dataset, by calling the
PATCH
endpoint and pass thesbit
value of the dataset (returned when dataset is registered) in theclose
parameter. The body can be left empty.
- In order to see the message, connect to the configured
queueOperations
Redis instance in a client of your choice.
Edited by Maggie Salak