readJournal
Purpose and behavior
Section titled “Purpose and behavior”Return a journal’s events in chronological order, reading its index at exactly reference.revision. Rejects with TransportConflict when the index has moved or a segment is missing, and with an error on a cycle or when maxEntries or maxBytes is exceeded.
Complete example and detailed rules.
Parameters and properties
Section titled “Parameters and properties”optionsRequiredReadJournalOptionsTransport, pinned journal index revision and traversal bound.options.referenceRequiredTransportReferenceJournal index reference, usually DispatchResult.logReference; the index must still have this revision.options.maxEntriesOptionalnumber | undefinedMost events to read, default 100000; a longer chain rejects.options.maxBytesOptionalnumber | undefinedTotal bytes of event segments to read, default 64 MiB; exceeding it rejects.options.transporterRequiredTransportCaller-owned object transport used by the store or operation. Closing a workflow or sandbox does not close this transport.