You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, the StaysInStation Pattern works by looking for a status=3followed by a status=4.
This however creates wrong result as there could be status=3, status=5, .... status=5, status=4;
but this would still trigger the pattern.
Also it detects a unique transport by using the station_id and the train_id which doesn't really work.
Expected behavior
A StaysInStation should only trigger when status=3 is directly before status=4.
It should work on a per train basis, maybe we could implement it like CountOfTrainsInStation in the way that we apply it on a keyed stream.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, the StaysInStation Pattern works by looking for a
status=3
followed by astatus=4
.This however creates wrong result as there could be status=3, status=5, .... status=5, status=4;
but this would still trigger the pattern.
Also it detects a unique transport by using the station_id and the train_id which doesn't really work.
Expected behavior
A StaysInStation should only trigger when status=3 is directly before status=4.
It should work on a per train basis, maybe we could implement it like CountOfTrainsInStation in the way that we apply it on a keyed stream.
The text was updated successfully, but these errors were encountered: