Skip to content

Make dep resource sync optional if it's already synced previously #17

@soichih

Description

@soichih

Currently, a task would fail to start up if any of the input resources are in non-OK status when it tries to sync inputs datasets even thouogh they are previously synced.

source resource status is non-ok .. will retry later

This is sad, because the task could be executed on active resource with previously synced input datasets and it's very rare that input datasets are modified.

To see if the input datasets are already synced, we can just look at dep.resource_ids, and if target resource id is listed there (the input dataset is already staged), make dataset syncing optional.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions