for the moment wound or be possible to build the BK fork as an artefact in the
twitter group in central so we don't need to build it ourselves.
Docs say the txn Id is an application supplied sequence number. It is required
to be non-decreasing. Users usually use either timestamp or offset.
What are the consequences of publishing two consecutive messages with the same
txn ids.
It simply must be non-decreasing- dup ids are ok.
Since txid is used for positioning, if you had a long series of identical
txids you might have to scan through a lot of records to find the record
you were really looking for if you were doing a lookup. Other than that
there should be no impact.
T
My quotation was raised because there was another discussion that resulted in
the answer that the txn Id was equiv to the index in raft. However i recall
something about uniqueness as well as upwards-only being important in raft
around "stage machine safety " and "log matching"
Perhaps they
>
> Perhaps they are not equivalent or perhaps I have the wrong idea?
They are not equivalent. Txnid is just a handy user defined sequence id.
The unique id is the DLSN. Uniqueness of this id is guaranteed by DLOG.
Thx
On Tue, Sep 20, 2016 at 11:01 AM, john.lonergan
wrote:
> My quotation was
I just tried to submit the infrastructure request for a user@ list, but it told
me that the list already exists. I guess another mentor beat me to it. You
can subscribe by sending an email to
user-subscr...@distributedlog.incubator.apache.org.
--Chris Nauroth
On 9/17/16, 8:18 PM, "Jay Juma"
