Fix: state not set in file-provided pipelines #909
Merged
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.
Description
This PR fixes the following bug.
Bug description
When Conduit is restarted with a pipeline, that was provided from a configuration file, the state is not correctly set after restart and lost.
Steps to reproduce
Expected behavior
After the restart, Conduit should start from the previous source position. Only new records are read.
Actual behavior
After the restart, Conduit re-reads all the records from source. Following can be found in logs:
Quick checks: