Skip to content

Resolve NXCALS-2433 "Schema desynchronization"

Jakub Wozniak requested to merge NXCALS-2433-Schema-desynchronization into develop

#Merge request template @acc-logging-team - please have a look for approval.

Fixing the problem with schema desync. It actually touches also partition id. Both schemaId & partitionId should be taken only from the entityHistory and not entity. This is with the assumption that the entityData will come here only with one history entry. The one that corresponds to the record timestamp. Is this is assured both ids should be taken from this history and not entity as the entity might have different values there (if the history is not the last one, but it can be as it depends only on the given record timestamp). This MR also fixes the problem with Kafka-ETLs for broken records - we just skip them.

Closes NXCALS-2433

Edited by Jakub Wozniak

Merge request reports