You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/11/04 17:11:01 UTC

[jira] [Commented] (BEAM-10795) Inconsistent Implementation of Expansion Service spec

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

Beam JIRA Bot commented on BEAM-10795:
--------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> Inconsistent Implementation of Expansion Service spec
> -----------------------------------------------------
>
>                 Key: BEAM-10795
>                 URL: https://issues.apache.org/jira/browse/BEAM-10795
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core, sdk-py-core
>            Reporter: Kevin Sijo Puthusseri
>            Priority: P3
>              Labels: Clarified
>
> The external API implementations in Java and Python don’t add the PTransform to the components map along with the fake impulses of the ExpansionRequest. I didn’t notice this and was adding it to the component map while implementing the same in Go. Python expansion service had no problem with this while the Java expansion service failed and was the first to point this failure. It was a simple fix and a non blocker but points to a possible inconsistent implementation of the Expansion Service spec (whose details I am unaware of)?



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