-
Notifications
You must be signed in to change notification settings - Fork 71
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
docs: Document that get_starting_timestamp
requires setting a non-null replication_key
#320
Comments
@edgarrmondragon is this still relevant? |
get_starting_timestamp
requires setting a non-null replication_keyget_starting_timestamp
requires setting a non-null replication_key
@tayloramurphy yeah, still relevant. We do have https://sdk.meltano.com/en/latest/incremental_replication.html now, but it wouldn't hurt to be explicit. |
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the |
Still relevant |
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the |
Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/322
Originally created by @edgarrmondragon on 2022-01-31 19:53:18
From slack thread: https://meltano.slack.com/archives/C01TCRBBJD7/p1643646009947879
Stream.get_starting_timestamp(context)
returnsNone
ifStream.replication_key
is not set for the stream. Documentation forget_starting_timestamp(context)
should indicate that requirement.The text was updated successfully, but these errors were encountered: