beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Groh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-3366) FnApiDoFnRunner should be registered for the ParDo URN
Date Sat, 16 Dec 2017 02:33:00 GMT

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

Thomas Groh updated BEAM-3366:
------------------------------
    Description: 
Currently it is registered for the "Java DoFn URN", which is too precise of a URN and is not
the URN on the PTransform with the default serialization path.

Potentially it could also be enforced that the DoFn has a "Custom Java DoFn URN", but that
is likely overly restrictive - the harness should be the required environment and be able
to deserialize the payload.

  was:Currently it is registered for the "Java DoFn URN", which is too precise of a URN and
is not the URN on the PTransform with the default serialization path.


> FnApiDoFnRunner should be registered for the ParDo URN
> ------------------------------------------------------
>
>                 Key: BEAM-3366
>                 URL: https://issues.apache.org/jira/browse/BEAM-3366
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-harness
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>              Labels: portability
>
> Currently it is registered for the "Java DoFn URN", which is too precise of a URN and
is not the URN on the PTransform with the default serialization path.
> Potentially it could also be enforced that the DoFn has a "Custom Java DoFn URN", but
that is likely overly restrictive - the harness should be the required environment and be
able to deserialize the payload.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message