beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Sisk (JIRA)" <>
Subject [jira] [Created] (BEAM-1639) Catch bad FractionConsumed values in the beam SDK.
Date Tue, 07 Mar 2017 18:56:38 GMT
Stephen Sisk created BEAM-1639:

             Summary: Catch bad FractionConsumed values in the beam SDK.
                 Key: BEAM-1639
             Project: Beam
          Issue Type: Bug
          Components: sdk-java-core
            Reporter: Stephen Sisk
            Assignee: Davor Bonaci
            Priority: Minor

getFractionConsumed in Sources are expected to return values between 0.0 and 1.0

I recently encountered a bug where a bad value of fractionConsumed was sent to a runner. Looking
through the beam source, I couldn't find anywhere that we validate the value before we send
it (it could be there and I didn't see it, but given that I saw this error with a real source,
I don't believe it is.)

I think it'd be useful if the beam SDK caught this error at the time the value is returned
and at least generate a useful error in the logs (thus allowing the user to more easily debug
the issue)

This message was sent by Atlassian JIRA

View raw message