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
Currently, if a client triggers a VSCopy operation it runs for all tables that the client is reading changes from. There should be an option for a client to specify a list of tables that should run the VSCopy operation, rather than always copying all of them.
The use case addressed is that VSCopy is a costly operation and a user may only want to COPY a single or small subset of tables to avoid the downtime when the connector is not in real-time streaming mode, and doesn't want to load the downstream system unnecessarily if only certain tables needed the VSCopy.
The text was updated successfully, but these errors were encountered:
Feature Description
Currently, if a client triggers a VSCopy operation it runs for all tables that the client is reading changes from. There should be an option for a client to specify a list of tables that should run the VSCopy operation, rather than always copying all of them.
Slack discussion
Use Case(s)
The use case addressed is that VSCopy is a costly operation and a user may only want to COPY a single or small subset of tables to avoid the downtime when the connector is not in real-time streaming mode, and doesn't want to load the downstream system unnecessarily if only certain tables needed the VSCopy.
The text was updated successfully, but these errors were encountered: