Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Resilient-like functionality for TimeKey-Append Mode-Channels

Answered
Jan-Frederik Marx User

Which database system?: target is Snowflake on AWS

 

Additional details:

Can you make resilient work on TimeKey channels (in Append Mode) to detect duplicates? Documentation says "A row's existence is determined using the replication key known to HVR". What we've already discussed in support cases is the fact that our source system hardly provides any primary key. However, isn't the hvr_tx_seq - based on source rrn per journal receiver - a possibility to detect duplications?

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Edwin Fivetranner

    Hi Jan-Frederik,

    Resilience depends on HVR having a stable replication key to determine whether a row already exists on the target. In TimeKey Append Mode, we append change events rather than maintaining a single target row per source row, so the normal row-existence logic does not apply.

    Using hvr_tx_seq / source RRN per journal receiver might theoretically help identify some duplicate change events, but that would require us to treat it as a durable event identity and guarantee uniqueness/stability across retries, journal receiver boundaries, re-capture, refresh, and other recovery scenarios. That feels like a different product capability rather than a small enhancement to Resilient. It would not span all the databases we support as sources.

    So I would be hesitant to say this is generally possible without a deeper engineering design. At best, it sounds like project-sized work with limited applicability, and I’m not sure the reach justifies it based on the current demand. 

    Best regards,

    Edwin