BetaBetadraftBetapublishedBetareachedBetaAdds a remote mutation to the timeline. This methods assumes that the remote mutations come in correct order for their respective version, but has no ordering requirements across draft/published.
Example: [D1, D2, P1] (where D1 and P1 were mutations done to the draft and published version in the same transaction) is a valid input. [P1, D2, D1] is not valid since the mutation for the draft is out of order.
BetaBetaBetaMark that we've reached the earliest entry.
BetaBetaResolves a time reference.
Note that the chunk returned is only valid if the timeline stays constant. Once the timeline is updated, you must re-parse all references.
BetaBetaupdateChunks synchronizes the chunks to match the current state of the transactions array. After calling this method you need to invalidate all Chunks.
Timeline maintains information about the history of a document: Grouping raw translog entries into sensible groups, replaying and reconstructing different versions and abstract other details.
Note that this class by itself is not capable of fetching information, but will only organize and structure the incoming translog entries.
Hidden