DLSN and Sequence ID are system generated.
Transaction ID is user provided.
> > Any idea which way it is?
> > Thanks
> > Original message ----From: Leigh Stewart
> > Date: 20/09/2016 18:48 (GMT+00:00) To:
> > dev@distributedlog.incubator.apache.org Su
matching"
> Perhaps they are not equivalent or perhaps I have the wrong idea?
> Any idea which way it is?
> Thanks
> Original message From: Leigh Stewart
> Date: 20/09/2016 18:48 (GMT+00:00) To:
> dev@distributedlog.incubator.apache.org Subject: Re: Duplic
tching"
Perhaps they are not equivalent or perhaps I have the wrong idea?
Any idea which way it is?
Thanks
Original message From: Leigh Stewart
Date: 20/09/2016 18:48 (GMT+00:00) To:
dev@distributedlog.incubator.apache.org Subject: Re: Duplicate transaction ids
It simply mu
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
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.
