...
CDAP-18586: getApplicationSpecification() method in interface io.cdap.cdap.api.schedule.ProgramStatusTriggerInfo has been removed in CDAP 6.6.0, which can cause the CDAP build break if you are using this method.
Known Issues
SQL Server Replication Source
CDAP-19354 : The default setting for the snapshot transaction isolation level (snapshot.isolation.mode) is repeatable_read, which locks the source table until the initial snapshot completes. If the initial snapshot takes a long time, this can block other queries.
In case transaction isolation level doesn't work or is not enabled on the SQL Server instance, follow these steps:
Configure SQL Server with one of the following transaction isolation levels:
In most cases, set snapshot.isolation.mode to snapshot
If schema modification will not happen during the initial snapshot, set snapshot.isolation.mode to read_committed
For more information, see Enable the snapshot transaction isolation level in SQL Server 2005 Analysis Services.
2. After SQL Server is configured, pass a Debezium argument to the Replication job. To pass a
Debezium argument to a Replication job in CDAP, specify a runtime argument prefixed with source.connector, for example, set the Key to source.connector.snapshot.isolation.mode and the Value to snapshot.
...
For more information about setting a Debezium property, see Pass a Debezium argument to a Replication job.