Common violations of FSM-nature of Item
Constructor, ensuring that final Item
always contains sorted Record
s
Constructor, ensuring that final Item
always contains sorted Record
s
non-empty list (probably) received without particular order
Item
with same Record
s, but ordered by timestamp
Check if list of applications extracted from SKIPPED record are blocking current app
Check that Item
has a consistent state, e.g.
Check that Item
has a consistent state, e.g. it has a single id
Primary FSM-checking state, validating that no records refer to unexpected previous records, e.g.
Primary FSM-checking state, validating that no records refer to unexpected previous records, e.g. NEW is always first and FAILED always refers to some PROCESSING
Check that Item
was already processed by Application
Does not do any validations on Item
, e.g.
Check that Item
was already processed by Application
Does not do any validations on Item
, e.g. inconsistent state ids
won't make result different.
Assumes that item with Application(_, _, None, _)
covers
Application(_, _, Some(a), _)
and Application(_, _, Some(b), _)
,
making safe double-processing (e.g. loading to two storage targets) by same rdb-loader