[
https://issues.apache.org/jira/browse/BEAM-12007?focusedWorklogId=575670&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-575670
]
ASF GitHub Bot logged work on BEAM-12007:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Apr/21 18:32
Start Date: 01/Apr/21 18:32
Worklog Time Spent: 10m
Work Description: dpcollins-google commented on pull request #14294:
URL: https://github.com/apache/beam/pull/14294#issuecomment-812093808
Thank you @victuos for doing this. Unfortunately, I don't believe this will
work as written since Beam will not preserve any form of order on the publish
side through to Pub/Sub for the ordering key to be meaningful. The Beam model
is complex and not all aspects are well documented, this might be one of those
areas to improve. I would suggest closing this for now and keeping this jira
open for a future complete implementation. @victuos, what do you think?
--
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: 575670)
Time Spent: 1h 40m (was: 1.5h)
> Set message ordering key for Google Pubsub
> ------------------------------------------
>
> Key: BEAM-12007
> URL: https://issues.apache.org/jira/browse/BEAM-12007
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Victor Devos
> Priority: P2
> Labels: PubSubIO, gcp, pubsub, pubsubio
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Message ordering is currently not supported on the producer side.
> [https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/pubsub/PubsubMessage.java#L44]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
