-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature: Ad-hoc snapshot support #55
Comments
We have thought about having a similar feature, here's the relevant issue ConduitIO/conduit#944. The idea is to allow connectors to advertise a list of custom actions that the user can trigger. These actions would be triggered through Conduit (e.g. through a request to an API endpoint). IMO that would be a much nicer solution compared to (ab)using the 3rd party resource the connector is connecting to. It would allow the user to have a unified way to trigger these actions, regardless of the connector. The problem is that it's a feature that spans multiple repos, from conduit, through the connector protocol, the SDK and lastly the connector itself. This is quite a bit lower on our priority list though. It's not like we don't want to do these things, but it's a matter of finding the time. |
Glad to hear it is something that you've considered already, and in a more generalized way! No pressure though - as with anything I bring up, its just to document it for future attention. |
Feature description
Debezium has an ad-hoc snapshot mode, where you can manually trigger snapshots after the initial snapshot has already run.
This would be useful here.
The text was updated successfully, but these errors were encountered: