Fix trip duplication in Graph Builder DSJ mapping #5794
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
As detailed in #5793, querying passing times for a replaced DatedServiceJourney fails currently with a NullPointerException.
The root cause is the creation of a duplicated Trip object during graph building when resolving the reference to the ServiceJourney associated with a replaced DatedServiceJourney.
Since looking up a given Trip in a Timetable is based on object identity rather than object equality (see
OpenTripPlanner/src/main/java/org/opentripplanner/model/Timetable.java
Line 119 in d15e616
The issue can be solved by using a deduplicator when creating the Trip object during graph building.
Issue
Close #5793
Unit tests
Added unit test.
Documentation
No
Changelog