Planning for our "1.0" SDK release
This issue will be used to track and discuss those items we believe are required for a stable and robust v1.0
launch of the Tap and Target SDKs.
Tap SDK:
-
Fully implement selection metadata -
Implement state tracking for incremental sync -
Implement catalog discovery -
Implement a DatabaseStream class for DB-type sources (#74 (closed)) -
Support LOG_BASED replication for DB-type sources (#74 (closed)) -
Support the ACTIVATE_MESSAGE unofficial singer extension (#18 (closed))
Target SDK:
-
Support deleting (soft or hard deletes) when receiving the ACTIVATE_MESSAGE message type (unofficial singer extension) (#18 (closed))
Both SDKs:
-
Have sufficient tests, including unit tests and integration tests -
Include out-of-box CI templates (e.g. for instance, with Github Actions)
Call for Comments
Want to suggest other must-have features for our 1.0
release checklist? Please add your feedback in the comments below.
Edited by AJ Steers