nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Parker <mrcspar...@gmail.com>
Subject Re: NIFI RabbitMQ Processor
Date Wed, 07 Oct 2015 15:05:46 GMT
Yes.   They are.  I will add them to the issues list.  Thanks for this!

I am going to continue working on this later next week.  I had to focus on
another project for the last week,



On Wed, Oct 7, 2015 at 5:23 AM, DAVID SMITH <davidrsmith@btinternet.com>
wrote:

> Chris
>
> I have tried running these processors and I have a couple of observations:
>
> 1) You may want to include a failure relationship, I found that when I was
> trying to connect to the broker which was not local server and i couldn't
> connect the processor was constantly yielding.
> 2) You may want to consider putting in a polling timer, as it currently
> polls the broker every milli second which seems a bit excessive & cpu
> intensive
> 3) The password field should be set to sensitive to hide the password
> 4) You may want to consider adding a ssl/tls option for connectivity as
> well as username/password.
>
> I hope these observations are of some help to you.
>
> Dave
>
> Sent from Yahoo! Mail on Android
>
> ------------------------------
> * From: * Chris Parker <mrcsparker@gmail.com>;
> * To: * <dev@nifi.apache.org>;
> * Subject: * NIFI RabbitMQ Processor
> * Sent: * Thu, Oct 1, 2015 12:47:35 AM
>
> I have started a NIFI RabbitMQ module:
>
> https://github.com/MDL/nifi-rabbitmq-bundle
>
> What works:
>
> - Direct exchanges.  Light workloads have been tested.  A few million
> items have been pushed through the system without any problems.  I have
> also run it for a few hours at a time without problem.
>
> What needs to be done:
>
> - It doesn’t have full documentation or tests yet (I can’t find an example
> of a mocked RabbitMQ server).
> - It also only supports direct exchanges.
>
> I will add multiple exchange types early next week.  I am also going to be
> testing this over a heavy load over the course of the next few weeks.
>
> I didn’t create a ticket since it isn’t ready to be used in a production
> system yet.  This is more of a heads up.  If you have any feedback, please
> let me know.
>
> Thanks,
> Chris Parker
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message