Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(data-warehouse): Dont read last incremental value when the pipeline is being reset #27877

Merged
merged 2 commits into from
Jan 24, 2025

Conversation

Gilbert09
Copy link
Member

Changes

  • When resetting the pipeline, don't use the stored last_incremental_value - instead use None to ensure all values are read from the source

@Gilbert09 Gilbert09 requested a review from a team January 24, 2025 18:41
@Gilbert09 Gilbert09 enabled auto-merge (squash) January 24, 2025 18:45
@Gilbert09 Gilbert09 disabled auto-merge January 24, 2025 19:04
@Gilbert09 Gilbert09 force-pushed the tom/reset-incremental-value branch from 63be16c to c63e52d Compare January 24, 2025 19:07
@Gilbert09 Gilbert09 enabled auto-merge (squash) January 24, 2025 19:07
@Gilbert09 Gilbert09 merged commit 7fd095f into master Jan 24, 2025
92 checks passed
@Gilbert09 Gilbert09 deleted the tom/reset-incremental-value branch January 24, 2025 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants