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

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

                Author: ASF GitHub Bot
            Created on: 10/Jan/20 19:39
            Start Date: 10/Jan/20 19:39
    Worklog Time Spent: 10m 
      Work Description: boyuanzz commented on pull request #10552: Revert 
"[BEAM-8932] [BEAM-9036] Revert reverted commit to use PubsubMessage as the 
canonical type in beam client"
URL: https://github.com/apache/beam/pull/10552
 
 
   Reverts apache/beam#10474
   Revert this change again because incompatible proto changes break dataflow. 
Further investigation is needed.
   
   R: @TheNeuralBit 
   cc: @dpcollins-google 
 
----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 370026)
    Time Spent: 12h 10m  (was: 12h)

> Expose complete Cloud Pub/Sub messages through PubsubIO API
> -----------------------------------------------------------
>
>                 Key: BEAM-8932
>                 URL: https://issues.apache.org/jira/browse/BEAM-8932
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model
>            Reporter: Daniel Collins
>            Assignee: Daniel Collins
>            Priority: Major
>          Time Spent: 12h 10m
>  Remaining Estimate: 0h
>
> The PubsubIO API only exposes a subset of the fields in the underlying 
> PubsubMessage protocol buffer. To accomodate future feature changes as well 
> as for greater compatability with code using the Cloud Pub/Sub apis, a method 
> to read and write these protocol messages should be exposed.



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

Reply via email to