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

Community

Other: HVR Restrict Contexts Enabled By Default

Answered
Zack Soderquist User
  • Edited

We use the HVR soft delete feature and have had incidents where someone refreshes a table and forgot to check the Context for compare_deleted and refresh_keep_deletes. This caused a data loss and a LOT of effort to recover the records. This was on a table with over 1 billion records.

This happened because those two contexts are not enabled/checked by default. 

It would be huge risk avoidance to be able to set a Restrict Context to be turned on by default during a refresh or compare. The person performing the refresh/compare could still turn them off, but they would be checked by default. For users that have other contexts created, it might also be useful to set them to be checked by default instead of unchecked by default. Maybe this could be an option when setting up the Restrict channel action.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Mark Van de Wiel User

    Zack,

    Thank you for your suggestion. I am awfully sorry to hear that you lost records as a result of not selecting the context to protect soft-deleted records.

    I will discuss with the team how we can lower the likelihood that this happens again.

    Thank you,
    Mark.

  • Mark Van de Wiel User

    Hi Zack,

    Have you considered defining/using an alternative Restrict condition. E.g.

    Restrict Context=!refresh_purge_deletes, RefreshCondition="{hvr_is_deleted} <> 0"

    This condition would be enabled in all cases, unless you run refresh with the Context refresh_purge_deletes. I.e. it would flip the default refresh behavior HVR creates when you define a soft delete channel.

    Hope this helps.

    Mark.

  • Zack Soderquist User

    That would give me a context to delete soft deleted records. But that would not prevent deleting soft deleted records during a normal refresh.