Exception handling in incremental refresh (!249) · Merge requests · OSDU Software / OSDU Data Platform / Consumption Services / GeoSpatial · GitLab

Ankita Srivastava requested to merge 453_HandleOSDUException_Refresh into master Jul 10, 2024

Type of change

[ X] Bug Fix
Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)
#453 (closed)

Does this introduce a change in the core logic?

[YES/NO] NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

AWS
Azure
GCP
IBM

Does this introduce a breaking change?

[YES/NO] NO

What is the current behavior?

In case of any OSDU exception, GCZ will miss records for refresh during that time period

What is the new/expected behavior?

GCZ will pickup from last successful refresh

Have you added/updated Unit Tests and Integration Tests?

Any other useful information