Treat Duplicates in Lookup Table Like Lookup Failures
Registered by
Phill
Currently, any duplicate in the a lookup table cause an exception however, if the multiple-choice may only be relevant for some or no records being processed through the pipeline. Instead, it would be better to treat them similarly to lookup failures but trace the duplicate keys. A more specific exception for this scenario might also be needed.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
