Event Hubs, Offset not mapped properly from ReceivedEventData -> Checkpoint

[codynolf-cnhi]

Query/Question
I am struggling to understand why the offset from a ReceivedEventData is losing its value (changing from correct value to 0) when I invoke ProcessorPartitionClient::UpdateCheckpoint. I have created my own CheckpointStore (just writes local json file) which gets called from the ProcessorPartitionClient, all good here. The problem is when I get the Checkpoint object from the signature the offset is now 0 instead of the proper value. SequenceNumber is mapping properly.

I noticed this change which did confuse me at first until i noticed it was recent, but this should not matter as my local offset is Int64 type.

Am I going crazy? Or is something not working like it should here.

Before Calling UpdateCheckpoint:

After UpdateCheckpoint is invoked and makes it way to my CheckpointStore implementation:

Why is this not a Bug or a feature Request?
I am new to open source so I wanted to put a query in first for a sanity check before I open a bug.

Setup (please complete the following information if applicable):

• OS: Windows WSL using .devcontainer -> mcr.microsoft.com/devcontainers/cpp:1-ubuntu-24.04)
• IDE : vscode
• Version of the Library used: 1.0.0-beta.10

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• [ x] Query Added
• [ x] Setup information Added

[LarryOsterman]

Thank you for your feedback.

FWIW, the "Offset" property has always been a string property - the Azure SDKs were incorrectly treating it as a numeric property, this has been fixed in all the existing Azure SDKs.

Looking at the code for UpdateCheckpoint, if the ReceivedEventMessage has both an Offset and a SequenceNumber, then both should be presented to the checkpoint store.

Can you verify that the ReceivedEventMessage has both attributes set?

[codynolf-cnhi]

Hello, I appreciate the reply. Good to know about the Offset data type, I was only confused at first just because of the differences bewtween latest and my local.

As for your question Can you verify that the ReceivedEventMessage has both attributes set? Yes, it looks like both of these are set in the ReceivedEventMessage , I believe this is my first screenshot in the description. If you agree, I can double check this and put in a bug ticket if I can reproduce.