[ 
https://issues.apache.org/jira/browse/BEAM-5967?focusedWorklogId=335624&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-335624
 ]

ASF GitHub Bot logged work on BEAM-5967:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Oct/19 17:00
            Start Date: 29/Oct/19 17:00
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on issue #8496: [BEAM-5967] Add 
handling of DynamicMessage in ProtoCoder
URL: https://github.com/apache/beam/pull/8496#issuecomment-547526362
 
 
   Hey @TheMatrix97! I think this made it into the 2.17.0 release cut that 
happened last week. Usually it takes a few weeks to get a release ready after 
the cut. When it's finished there will be an announcement on [the mailing 
list](https://lists.apache.org/[email protected]) and [the 
blog](https://beam.apache.org/blog/).
   
   Alternatively you should be able to get this feature if you use the 
2.18.0-SNAPSHOT version.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 335624)
    Time Spent: 7h 50m  (was: 7h 40m)

> ProtoCoder doesn't support DynamicMessage
> -----------------------------------------
>
>                 Key: BEAM-5967
>                 URL: https://issues.apache.org/jira/browse/BEAM-5967
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>    Affects Versions: 2.8.0
>            Reporter: Alex Van Boxel
>            Assignee: Alex Van Boxel
>            Priority: Major
>             Fix For: 2.17.0
>
>          Time Spent: 7h 50m
>  Remaining Estimate: 0h
>
> The ProtoCoder does make some assumptions about static messages being 
> available. The DynamicMessage doesn't have some of them, mainly because the 
> proto schema is defined at runtime and not at compile time.
> Does it make sense to make a special coder for DynamicMessage or build it 
> into the normal ProtoCoder.
> Here is an example of the assumtion being made in the current Codec:
> {code:java}
> try {
>   @SuppressWarnings("unchecked")
>   T protoMessageInstance = (T) 
> protoMessageClass.getMethod("getDefaultInstance").invoke(null);
>   @SuppressWarnings("unchecked")
>   Parser<T> tParser = (Parser<T>) protoMessageInstance.getParserForType();
>   memoizedParser = tParser;
> } catch (IllegalAccessException | InvocationTargetException | 
> NoSuchMethodException e) {
>   throw new IllegalArgumentException(e);
> }
> {code}



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

Reply via email to