You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2019/10/15 21:21:00 UTC

[jira] [Commented] (BEAM-8172) Add a label field to FunctionSpec proto

    [ https://issues.apache.org/jira/browse/BEAM-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952300#comment-16952300 ] 

Kenneth Knowles commented on BEAM-8172:
---------------------------------------

I'd suggest "debug_string" to make it clear that there is no semantic content.

> Add a label field to FunctionSpec proto
> ---------------------------------------
>
>                 Key: BEAM-8172
>                 URL: https://issues.apache.org/jira/browse/BEAM-8172
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Chad Dombrova
>            Assignee: Chad Dombrova
>            Priority: Major
>
> The FunctionSpec payload is opaque outside of the native environment, which can make debugging pipeline protos difficult.  It would be very useful if the FunctionSpec had an optional human readable "label", for debugging and presenting in UIs and error messages.
> For example, in python, if the payload is an instance of a class, we could attempt to provide a string that represents the dotted path to that class, "mymodule.MyClass".  In the case of coders, we could use the label to hold the type hint:  "Optional[Iterable[mymodule.MyClass]]".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)