[
https://issues.apache.org/jira/browse/BEAM-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547384#comment-17547384
]
Kenneth Knowles commented on BEAM-5972:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/19145
> Multiple ApiServiceDescriptors in InstructionRequest leading to unintentional
> multiple instances of objects in the Java SDK
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-5972
> URL: https://issues.apache.org/jira/browse/BEAM-5972
> Project: Beam
> Issue Type: New Feature
> Components: java-fn-execution
> Reporter: Alex Amato
> Priority: P3
>
> I noticed that that two separate instances of the ApiServiceDescriptors exist
> in the instruction request.
> This is used as a key to access the BeamFnDataGrpcMultiplexer, and new
> instances are created if a differing ApiServiceDescriptors is used to access
> it.
> The InstructionRequest .
> I encountered this while trying to add some code in ProcessBundleHandler that
> needed to access the BeamFnDataGrpcMultiplexer and I used the ProcessBundle
> root ApiServiceDescriptor.
> One usage is in the ProcessBundleDescriptor. The second comes from the
> RemoteGrpcPort. Which actually comes out of a serialized bytes field. See
> RemoteGrpcPortWrite::fromPTransform
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
