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.

Sign up for GitHub

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

Jump to bottom

feat: Allow developers to customise when taps emit state #2879

Open
ReubenFrankel opened this issue Feb 13, 2025 · 0 comments
Open

feat: Allow developers to customise when taps emit state #2879

ReubenFrankel opened this issue Feb 13, 2025 · 0 comments
Labels
Accepting Pull Requests kind/Feature New feature or request Type/Tap Singer taps valuestream/SDK

Comments

@ReubenFrankel
Copy link
Contributor

ReubenFrankel commented Feb 13, 2025 •
edited
Loading

Feature scope

Taps (catalog, state, tests, etc.)

Description

Currently you can customise STATE_MSG_FREQUENCY per stream class to control after how many records a state message is emitted. It would be good to be able to override this behaviour in a more nuanced manner, such as to emit state at regular date-time intervals based on the previous state replication key value (timestamp).

A should_emit_state method was proposed in Slack.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Accepting Pull Requests kind/Feature New feature or request Type/Tap Singer taps valuestream/SDK
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edgarrmondragon @ReubenFrankel