You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:17 UTC
[jira] [Commented] (BEAM-7433) RabbitMQMessage coder can't be
registered when using Google Cloud Dataflow
[ https://issues.apache.org/jira/browse/BEAM-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174714#comment-17174714 ]
Beam JIRA Bot commented on BEAM-7433:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> RabbitMQMessage coder can't be registered when using Google Cloud Dataflow
> --------------------------------------------------------------------------
>
> Key: BEAM-7433
> URL: https://issues.apache.org/jira/browse/BEAM-7433
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.12.0
> Reporter: Nicolas Delsaux
> Priority: P2
> Labels: stale-P2
>
> When using Google cloud Dataflow, coders registered through
> {code:java}
> pipeline.getCoderRegistry().setCoderForClass(...){code}
> Don't seem to be really registered. As a consequence, RabbitMqMessage objects are not correctly serialized.
> I would love to provide more details, unfortunatly I was not able to produce a valid debugging session to dive into details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)