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

Community

Location or Environment actions improvement

Naresh Kumar Grandi User
We request the addition of the following metadata variables in Fivetran HVR to achieve feature parity with Qlik Replicate and support enterprise CDC migration use cases

Requested New HVR Metadata Variables

  • Source Database User

    • Qlik: $AR_H_USER
    • Proposed HVR: {hvr_src_user}
    • Purpose:
      • Data lineage
      • Compliance auditing
      • Application-level troubleshooting
      • User activity tracking
    • Currently unavailable in HVR. We have something like hvr_cap_user but it is getting the details from HVR Location  but not the original transaction user from Database logs 

  • Source Transaction ID

    • Qlik: $AR_H_TRANSACTION_ID
    • Proposed HVR: {hvr_tx_id}
    • Purpose:
      • End-to-end transaction tracing
      • CDC validation
      • Data reconciliation
      • Multi-hop replication troubleshooting
    • Currently unavailable in HVR.  hvr_tx_id  ??
  •  

  • Source Log Position / LSN / SCN / Stream Position

    • Qlik: $AR_H_STREAM_POSITION
    • Proposed HVR: {hvr_stream_position}
    • Purpose:
      • Restartability
      • CDC auditing
      • Exact source log sequencing
      • Downstream reconciliation
    • Existing {hvr_tx_scn} for oracle/{hvr_tx_sequence_number} for Db2 Iseris  are available but not supporting for DB2 zO/S
  • Oracle SCN/SQL Server LSN/DB2 RBA/Postgres WAL Position/MySQL Binlog Position

Business Justification

  • Preserve existing Qlik Replicate functionality during migration
  • Enable audit columns in S3, Kafka, and database targets.

Request

Please expose the following metadata as native HVR expression

1
{hvr_src_user}
2
{hvr_tx_id}
3
{hvr_stream_position}
Show more lines

and make them available for:

  • IntegrateExpression
  • CaptureExpression
  • FileIntegrate
  • Kafka targets
  • S3 targets
  • API/metadata access

This enhancement would significantly simplify enterprise migrations from other replication  tools to  Fivetran HVR and improve CDC auditing, lineage, and operational visibility

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Naresh Kumar Grandi User

    Sample data: 

    PX_ACTION  PX_USER ($AR_H_USER) PX_TIMESTAMP DB2_ROW_CRT_TS  PX_UOWID( $AR_H_TRANSACTION_ID) PX_RESTART( $AR_H_STREAM_POSITION)            
    UPDATE BF19DX   03:18.1 03:13.0 0000000000028B1F546647D8  10575;639204481990437180;20240209171642195714|000000028B1F5466B7480001
    UPDATE BF19DX   03:18.1 03:13.0 0000000000028B1F546647D8  10575;639204481990437350;20240209171642195714|000000028B1F5466C67C0001
    UPDATE BF19DX   03:18.1 03:13.0 0000000000028B1F546647D8  10575;639204481990437520;20240209171642195714|000000028B1F5466D5EE0001
    UPDATE BF19DX   03:18.1 03:13.0 0000000000028B1F546647D8  10575;639204481990437680;20240209171642195714|000000028B1F5466E5EB0001
    UPDATE BF19DX   03:18.1 03:13.0 0000000000028B1F546647D8  10575;639204481990437860;20240209171642195714|000000028B1F5466F5070001