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

Community

Destination Improvement: Expose HVR_SEQ as Numeric in RRN / S3 JSON Output

Answered
Naresh Kumar Grandi User

Hello Fivetran HVR Team,

We would like to submit a feature enhancement request related to how HVR_SEQ is exposed AS400 RRN  key and S3 JSON targets.

Request:
Provide an option to expose HVR_SEQ as a numeric (integer / bigint) value instead of the current hexadecimal representation in RRN and S3 JSON outputs.
 
In HVR, HVR_SEQ represents the deterministic ordering of changes and is defined as:
HVR_SEQ = TRANSACTION_ORDER | OPERATION_ORDER          <high-order-sequence> | <low-order-sequence>
 
Eg:  000000000E5B3BEF00000004EADBE7BA|7FFFFFFFFFFA
 

Problem Statement

For downstream processing, we rely on this sequence value as part of the record selection and delta extraction criteria.

However:

  • Hexadecimal values are not natively usable for numeric comparison in many downstream platforms
  • Additional parsing / conversion logic is required in every consumer
  • This introduces complexity, performance overhead, and potential inconsistency across pipelines

Why Numeric HVR_SEQ Is Needed

Providing HVR_SEQ as a numeric type would allow:

  • ✅ Direct use in delta capture logic
  • ✅ Simple greater‑than / less‑than comparisons
  • ✅ Consistent behavior with Qlik Replicate change sequence columns
  • ✅ Cleaner Stage → Raw → Transform (Trn) pipelines
  • ✅ Reduced custom logic in downstream data loads

This sequence value is critical for:

  • Incremental loads
  • Record ordering
  • Deterministic reprocessing
  • Audit and replay scenarios
We are open to any of the following approaches:
HVR_SEQ_NUM in NUMARIC /BIGINT Formats

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Edwin Fivetranner

    Hi Naresh,

    Thank you for the detailed enhancement request and for clearly outlining the use case.

    We understand that exposing HVR_SEQ as a numeric value instead of a hexadecimal representation would simplify downstream processing, particularly for delta logic, ordering, audit scenarios, and deterministic reprocessing. 

    We will review this internally with our engineering team to evaluate feasibility, design implications, and potential impact. If needed, we may reach out for further clarification.

    We will update you once we have more clarity on the next steps and prioritization.

    Best regards,

    Edwin

  • Naresh Kumar Grandi User

    Thank you and keep us posted the updates on the status