Search Results for

    Show / Hide Table of Contents

    Namespace Akka.Persistence.TCK.Query

    Classes

    AllEventsSpec

    ColorFruitTagger

    CurrentAllEventsSpec

    CurrentEventsByPersistenceIdSpec

    CurrentEventsByTagSpec

    CurrentPersistenceIdsSpec

    EventsByPersistenceIdSpec

    EventsByTagSpec

    FromEndOffsetSpec

    Verifies that a read journal honors the FromEnd ("last N events") query offset, which begins a query at the Nth event from the end of history rather than from the beginning.

    This is the cross-backend contract for FromEnd. It exercises the full matrix of {by-tag, all-events} × {current, live} against an interleaved, multi-persistence-id fixture that mixes tagged and untagged events. The interleaving is deliberate: a single-persistence-id fixture cannot distinguish a backend that resolves the from-end position correctly (per-tag count for by-tag queries, total count for all-events queries) from one that naively resolves both against a single global ordinal, because the two coincide only when there is one writer and every event carries the tag. The ...should_count_per_tag_... test pins exactly that distinction.

    Only read journals that support FromEnd should inherit from this spec. Backends that cannot resolve a from-the-end position (e.g. those without a global ordering) should not opt in. A backend must also implement the current counterpart of every query it supports here, since the spec uses the current queries to confirm writes are visible before resolving a from-end window. Individual tests are virtual so a backend can override or skip the dimensions it does not implement.

    PersistenceIdsSpec

    In this article
    Back to top
    Contribute
    • Project Chat
    • Discussion Forum
    • Source Code
    Support
    • Akka.NET Support Plans
    • Akka.NET Observability Tools
    • Akka.NET Training & Consulting
    Maintained By
    • Petabridge - The Akka.NET Company
    • Learn Akka.NET