I'm seeing what I think is a bad record when using tap-mssql wintersrd variant with log based replication. When there are no changes the tap is sending a null record into the stream before moving onto the next stream. Wondering if anyone else has encountered this behaviour as it chokes my snowflake target as it then tries to merge a record with all nulls. I've reported as an issue in the repo (https://github.com/wintersrd/pipelinewise-tap-mssql/issues/93) however as I'm new to this it could be something related to my setup. Hoping someone here might be able to offer some assistance This is the record issued after the SCHEMA for the stream.

{
  "type": "RECORD",
  "stream": "locality-Suburb",
  "record": {
    "SuburbId": null,
    "StateId": null,
    "PostcodeName": null,
    "RegexPostcodeName": null,
    "Name": null,
    "RegexName": null,
    "IsActive": null,
    "LGA": null,
    "DateConfirmed": null,
    "ConfirmerId": null,
    "MunicipalityId": null,
    "Town": null,
    "SchedulingRegionId": null,
    "SchedulingRegionName": null,
    "RPDataLocationId": null,
    "_sdc_operation_type": null,
    "_sdc_lsn_commit_timestamp": null,
    "_sdc_lsn_deleted_at": null,
    "_sdc_lsn_value": null,
    "_sdc_lsn_seq_value": null,
    "_sdc_lsn_operation": null
  },
  "version": 1729457923663,
  "time_extracted": "2024-10-20T20:58:43.752838Z"
}