fix(helpers): use isIncremental
instead of SyncPolicy.FullSync
#7773
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pr-type/bug-fix
,pr-type/feature-development
, etc.Summary
What does this PR do?
Use
isIncremental
instead ofSyncPolicy.FullSync
.Var
syncPolicy
in code:= args.Ctx.TaskContext().SyncPolicy()
comes from_devlake_pipelines
.When we collect data, then change its time range, set an early start time, collect data again. It should collect data fully, but
_devlake_pipelines.full_sync
is zero, which stands for false. So inNewStatefulApiCollectorForFinalizableEntity
we should useisIncremental
.Does this close any open issues?
Closes #7772 #7766.
Maybe related #7739.
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.