[
https://issues.apache.org/jira/browse/BEAM-8932?focusedWorklogId=369235&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-369235
]
ASF GitHub Bot logged work on BEAM-8932:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jan/20 18:28
Start Date: 09/Jan/20 18:28
Worklog Time Spent: 10m
Work Description: chamikaramj commented on issue #10476:
[BEAM-8932][Cleanup] Move external PubsubIO hooks outside of PubsubIO.
URL: https://github.com/apache/beam/pull/10476#issuecomment-572690734
In general, are changes to PubSubIO in this and other PRs you authored
backwards compatible ? If change changes are not backwards compatible (if users
cannot upgrade Beam without changes to their pipelines) i think this needs a
deeper look since Beam guarantees backwards compatibility across minor
versions. This is OK for external transforms part which is experimental but
PubSubIO is used in production by many users.
----------------------------------------------------------------
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: 369235)
Time Spent: 11h 10m (was: 11h)
> 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: 11h 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)
