Class InsertOutcome
-
- All Implemented Interfaces:
public class InsertOutcomeOutcome of PingsDao.reserveAndInsert. Strategies use this to drive their telemetry side effects (the DAO itself stays telemetry-free).
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description public final classInsertOutcome.InsertedFree slot existed within
maxEntries; ping was inserted with no eviction.public final classInsertOutcome.InsertedWithEvictionThe table was at the cap; evicted was removed to make room and ping was inserted in its place. Caller should emit a
PING_EVICTED_WHILE_INSERTING_*telemetry event for evicted.public final classInsertOutcome.DuplicateA row with ping.id already exists. ping was NOT inserted and no existing row should be evicted. Caller should emit a duplicate-ping telemetry event.
public final classInsertOutcome.RejectedThe table was at the cap and no eligible existing row could be displaced under the eviction policy (e.g. a NORMAL insert with no NORMAL row to drop). ping was NOT inserted. Caller should emit a
PING_DB_MAX_LIMIT_REACHEDtelemetry event and fail the ping back to its listener.
-