Add the ability to flag various conditions in a RawEvent
When an event times out in the event store, has duplicate fragment IDs, or has some other exceptional condition, we should be able to flag it, and possibly route it to a different disk file (stream).
This issue requests the addition of functionality in RawEvent (and whatever other classes may need to be changed) to support the indication of exceptional conditions.
We should also provide a sample art module (or whatever the correct mechanism is) to demonstrate the routing of events with issues to different disk files.
#8 Updated by Eric Flumerfelt over 1 year ago
- Status changed from New to Closed
This functionality is mostly already present. RawEventHeader includes the "is_complete" flag (though RawEventHeader is not currently stored in art events, see #20815). MissingDataCheck_module fulfills the rest of the requirements, though "has duplicate fragment IDs" would have to be handled in feature/3186_SMEM_FragmentIDChecking.