Currently the Oracle connector does allow setting the event.processing.failure.handling.mode option to SKIP, WARN, or FAIL to handle situations where LogMiner failed to reconstruct the SQL; however, this setting does not extend to handling DML parser errors.

In light of DBZ-8034, we should probably extend this setting also to include the failure to parse DML event via the DmlParser contract.

By doing so, this would allow these corner cases where a specific DML parse failed to be recoverable by having the user execute an incremental snapshot for the row in question. By logging the details for the change, users would be able to get enough context from the skipped event to easily focus on an incremental snapshot for that individual row or rows that needed to be skipped.