You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/08/24 21:06:00 UTC

[jira] [Assigned] (BEAM-1639) Catch bad FractionConsumed values in the beam SDK.

     [ https://issues.apache.org/jira/browse/BEAM-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davor Bonaci reassigned BEAM-1639:
----------------------------------

    Assignee:     (was: Davor Bonaci)

> Catch bad FractionConsumed values in the beam SDK.
> --------------------------------------------------
>
>                 Key: BEAM-1639
>                 URL: https://issues.apache.org/jira/browse/BEAM-1639
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Stephen Sisk
>            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
(v6.4.14#64029)