You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, the API allows to order by a created timestamp, but does not allow filtering based on that.
The API supports pagination based on a uuid - which isn't incremental.
The current SDK behavior is that if I define the id as the replication_key, something like ff31e109-f873-41b6-9f1c-2d88b5bf6a2a will be tracked as the "latest record", which isn't true. It just happens to be the "highest" because of the 'ff...' in front.
So, what I would instead want to have is an API where is_sorted = True, but that would not check for the replication_key to be an increment, and instead trust that the last one seen is the most recent one.
The text was updated successfully, but these errors were encountered:
My need comes from trying to build a tap for the UserFlow API.
Documentation: https://userflow.com/docs/api#pagination
In short, the API allows to order by a created timestamp, but does not allow filtering based on that.
The API supports pagination based on a uuid - which isn't incremental.
The current SDK behavior is that if I define the id as the replication_key, something like ff31e109-f873-41b6-9f1c-2d88b5bf6a2a will be tracked as the "latest record", which isn't true. It just happens to be the "highest" because of the 'ff...' in front.
So, what I would instead want to have is an API where
is_sorted = True
, but that would not check for thereplication_key
to be an increment, and instead trust that the last one seen is the most recent one.The text was updated successfully, but these errors were encountered: