feat: add offset diagnostic logging and max_records_per_run limit #373
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.
Summary
max_records_per_runparameter to limit records processed per runMotivation
After PR #372 merge, analysis showed that 34% of transformations (73/215) have stuck offsets despite successful processing. This PR adds:
Changes
max_records_per_runparameter toBaseBatchTransformStep.__init__get_full_process_idswhen max_records_per_run is setstore_batch_resultwhen offset not calculatedrun_fullwhen changes.offsets is emptyBatchTransformandDatatableBatchTransformdataclasses