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

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

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

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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: P2
>              Labels: Clarified, stale-P2
>
> 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)