Getting offset and sequence number from event data rather than amqp annotations.

[j7nw4r]

This PR addresses: #3073

Properly retrieve the offset and sequence numbers to properly store checkpoints.

[Copilot]

Pull Request Overview

This PR fixes the improper extraction of offset and sequence numbers for Event Hub checkpoints. The existing code was manually parsing AMQP message annotations to retrieve these values, which was error-prone and redundant. The fix leverages the existing accessor methods on ReceivedEventData to directly obtain the offset and sequence number values.

• Removes manual AMQP annotation parsing logic for offset and sequence numbers
• Uses direct accessor methods event_data.offset() and event_data.sequence_number() instead
• Simplifies the checkpoint update flow by removing unnecessary error handling for annotation parsing

[j7nw4r]

@LarryOsterman Please review. I went back to a structure similar to the original. I updated the annotation labels used to use the same labels as the .offset() and .sequence_number() functions. I also cleaned up the logic to make things more readable (imo).

[j7nw4r]

@microsoft-github-policy-service agree company="Microsoft"

[LarryOsterman]

/cla help

[LarryOsterman]

@microsoft-github-policy-service rerun

[LarryOsterman]

@microsoft-github-policy-service rerun

[heaths]

/check-enforcer evaluate

[heaths]

With this in, can we get a release out? I have #3143 in a draft state waiting on this, more or less.