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

Community

Other: HVR Replication : CycleByteLimit value change

Not planned
Abhinav Joshi User

HI Team 

We currently have a table called Charge that is huge and has lot of updates. This gets streamed from Oracle to Snowflake using HVR. Many times we encounter the coalesece issue and in this case we manually change the cyclebytelimit to 1 and this resolved the issue. However after the process becomes stable , we cannot keep it to the same number as that will slow down stuff and hence we need to again reset the cyclebytelimit to its original value. We are wanting to see if Fivetran can do this programmatically on their end as this saves us a lot of time. 

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Mark Van de Wiel User

    Hi Abhinav,

    Does your table Change happen to have duplicates? Typically when we see coalesce issues the key is not correctly defined.

    I know you ask for changing the CycleByteLimit on the fly but in this case it feels to me that there is a problem that we should solve, rather than implement a workaround for you.

    Mark.