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

Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2016/06/25 17:05:37 UTC

[jira] [Updated] (BEAM-227) Log sdk version in worker-startup logs

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

Daniel Halperin updated BEAM-227:
---------------------------------
    Fix Version/s: Not applicable

> Log sdk version in worker-startup logs
> --------------------------------------
>
>                 Key: BEAM-227
>                 URL: https://issues.apache.org/jira/browse/BEAM-227
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-core
>            Reporter: Mark Shields
>            Assignee: Davor Bonaci
>             Fix For: Not applicable
>
>
> As a failsafe against bizzare jar versioning problems it would be great if the worker could simply print its build version (as a hard-coded, impossible to mess up string)
> I just saw a customer who's jars were all tagged 1.5.1 but their contents were 1.5.0. I am not able rightly to apprehend the kind of confusion of implementation that could provoke such a scenario.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)