Re: NiFi questions

On Wed, May 2, 2018 at 10:00 PM, Andy LoPresto wrote: > Hi Clay, > > A common use case for NiFi and Kafka in conjunction is when you want the > capabilities of a message broker system like Kafka with very low latency > and multiple publishers/consumers, but you also have

Re: NiFi questions

Thanks Andy for the feedback On Wed, May 2, 2018 at 10:00 PM, Andy LoPresto wrote: > Hi Clay, > > A common use case for NiFi and Kafka in conjunction is when you want the > capabilities of a message broker system like Kafka with very low latency > and multiple

Re: NIFI-5133: Guidance & help with tackling dependency version issues

I'm interested although it might consume some time since I don't know how big it is going to be. And I suppose it is better to capture it in a separate Jira. The summary could be upgrade and refactor GCP processor codebase or something like that. We could then make NIFI-5133 a dependent of the new

Re: NIFI-5133: Guidance & help with tackling dependency version issues

Sivaprasanna Ok makes sense. Are you in a position of interest/expertise/time to make those changes as well? Thanks On Thu, May 3, 2018 at 12:11 PM, Sivaprasanna wrote: > Hi. As I had mentioned, upgrading to the latest version of the library is > not as simple as I

Re: NIFI-5133: Guidance & help with tackling dependency version issues

Hi. As I had mentioned, upgrading to the latest version of the library is not as simple as I thought. Google Cloud team introduced many breaking changes. Many of the APIs (classes & methods) have been scrapped/replaced/modified/refactored/renamed. In short, a simple change of version may demand

Re: NIFI-5133: Guidance & help with tackling dependency version issues

Sivaprasanna I might not completely follow but is there a 3rd option to upgrade to a more recent library and solve the use of the proper jars problem(smaller nar)? Thanks On Thu, May 3, 2018 at 11:51 AM, Sivaprasanna wrote: > Hi > > I've started the initial works on

NIFI-5133: Guidance & help with tackling dependency version issues

Hi I've started the initial works on implementing Google Cloud Pub/Sub processors. The associated Jira ID is NIFI-5133 . This will go to the existing GCP bundle which currently has only the storage processors. Upon some inspection, I noticed the

NIFI-5070/NIFI-5049 patches available

Hi folks, I've sent both patches some time ago, I know you are very busy but please let me know if something else is required in both patches. Thanks in advance, Juan

Re: GetMongoDB : How to pass parameters as input to GetMongoDB processor

Brajendra, I would recommend an update to 1.6.0. It'll make your life a lot easier on this. I did that patch to GetMongo because I had a client that had an explosion of GetMongos due to that inflexibility. With that said, *be aware of this bug* in 1.6.0 w/ PutMongo if you use it and upgrade. It

Re: GetMongoDB : How to pass parameters as input to GetMongoDB processor

Hi, As Mike said: incoming relationship has been added for NiFi 1.6.0. https://issues.apache.org/jira/browse/NIFI-4827 Pierre 2018-05-03 14:09 GMT+02:00 Brajendra Mishra : > Hi Mike, > > I did attach the same in my previous mail. Well reattaching it again. >

RE: GetMongoDB : How to pass parameters as input to GetMongoDB processor

Hi Mike, I did attach the same in my previous mail. Well reattaching it again. Well error is at GetMongoDB Processor and error text is : "Upstream Connections is invalid because Processor does not allow upstream connections but currently has 1" Brajendra Mishra Persistent Systems Ltd.

Re: GetMongoDB : How to pass parameters as input to GetMongoDB processor

Brajendra, Looks like the image didn't make it. On Wed, May 2, 2018 at 11:36 PM Brajendra Mishra < brajendra_mis...@persistent.com> wrote: > Hi Mike, > > Thanks for responding. > > Here, I have attached missing image attachment. > > > > Brajendra Mishra > > Persistent Systems Ltd. > > > >