Closed rekby closed 7 months ago
Hi, do you think that it is really bug? topicWriter.WaitInitInfo(...)
returns InitInfo
which contains only LastSeqNum
field.
This object edits once, when writer initializes.
And when topicWriter.WaitInitInfo(...)
called, writer will always return same object with same values;
Also there is a test, which says that info
object should be idempotent
I see solution in writing function as example GetLastSeqNo
, which will return actual sequence number. What do you think?
In my case I need to deduplicate messages based on their seqNo, and I'm managing its value myself. At the moment, I'm obtaining information either through the WaitInitInfo() method or the deprecated topicoptions.WithOnWriterFirstConnected() method, where the seqNo is consistently -1.
For my use case, it would be beneficial to have methods like GetLastSeqNo() or GetInfo() implemented.
Bug Report
YDB GO SDK version: 3.55.0
topicWriter.WaitInitInfo(...)
always return LastSeqNum == -1 if topicwriter starts with optionWithWriterSetAutoSeqNo(false)