You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Alex Amato (JIRA)" <ji...@apache.org> on 2018/11/05 17:43:00 UTC
[jira] [Created] (BEAM-5972) Multiple ApiServiceDescriptors in
InstructionRequest leading to unintentional multiple instances of objects
in the Java SDK
Alex Amato created BEAM-5972:
--------------------------------
Summary: 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
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
(v7.6.3#76005)