You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Edin (JIRA)" <ji...@apache.org> on 2019/01/26 13:39:00 UTC
[jira] [Created] (BEAM-6515) Unable to read messages from RabbitMQ
as a continuous stream
Edin created BEAM-6515:
--------------------------
Summary: Unable to read messages from RabbitMQ as a continuous stream
Key: BEAM-6515
URL: https://issues.apache.org/jira/browse/BEAM-6515
Project: Beam
Issue Type: Bug
Components: io-java-gcp
Reporter: Edin
Assignee: Chamikara Jayalath
The RabbitMqIO connector does not work entirely as expected. Not passing {{withMaxReadTime}} gives a NullPointer exception. Exact error:
{code:java}
Exception in thread "main" java.lang.NullPointerException
at org.apache.beam.runners.direct.UnboundedReadEvaluatorFactory$UnboundedReadEvaluator.processElement(UnboundedReadEvaluatorFactory.java:169)
at org.apache.beam.runners.direct.DirectTransformExecutor.processElements(DirectTransformExecutor.java:160)
at org.apache.beam.runners.direct.DirectTransformExecutor.run(DirectTransformExecutor.java:124)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
It seems RabbitMqIO does not cover the case when messages received from RabbitMQ have messages of which timestamps are null. On Stackoverflow the following workaround is proposed:
[https://stackoverflow.com/a/54119782]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)