[BEAM-14536] Offsetrange tracker panics when splitting at 0.0 without claiming work

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.40.0
• Component/s: sdk-go
• Assignee: Danny McCormick
• Reporter: Danny McCormick
• Created: 31/May/22 15:53
• Updated: 01/Jun/22 17:51
• Resolved: 01/Jun/22 17:51

Description

Right now, if you try to call TrySplit on an offsetrange restriction with a fraction of 0.0 and without first claiming work, it sets the primary restriction to {Start, Start-1}. This causes newSplitResult to panic - https://github.com/apache/beam/blob/ff39fcb5229b15140e41a61bd09f7d590730e93a/sdks/go/pkg/beam/core/runtime/exec/sdf.go#L859

Issue Links

• links to: GitHub Pull Request #17782