Re: Subscribe me to Apache NiFi

Please send an email to dev-subscr...@nifi.apache.org On Sat, Dec 19, 2015 at 1:35 AM, Deepak Dixit wrote: > Kindly add to dev mailing list. > > -- > From: > > Deepak D Dixit > deepakdixit2...@gmail.com > +919028507537

Subscribe me to Apache NiFi

Kindly add to dev mailing list. -- From: Deepak D Dixit deepakdixit2...@gmail.com +919028507537

Re: Cluster Setup

I believe you are having issues related to hostname resolution on your nodes and NCM. By leaving the varies host properties in your NiFi properties file blank, they are resolving to localhost. Each stem thinks localhost is itself. Try filling in the properties either with FQDNs that each node can s

Re: discuss nifi 0.4.1

rgr that - will revert, save patch on ticket, plus this means someone can get Oleg's kafka tester patch reviewed there too. thanks On Fri, Dec 18, 2015 at 11:26 PM, Sean Busbey wrote: > with the Kafka client change backed out for 0.5.0, I'm good to go with > 0.4.1 on the rest of the changes. > >

Re: discuss nifi 0.4.1

with the Kafka client change backed out for 0.5.0, I'm good to go with 0.4.1 on the rest of the changes. On Fri, Dec 18, 2015 at 10:11 PM, Joe Witt wrote: > Sean, > > Yeah i don't disagree with that point. The caveat being it was only a > change to that client not a change to support the new cli

Re: Testing handling of static class methods

You could use PowerMock to either call private static methods directly or to mock them out. https://github.com/jayway/powermock/wiki/MockStatic https://github.com/jayway/powermock/wiki/MockPrivate https://github.com/jayway/powermock/wiki/BypassEncapsulation#invoking-a-private-method On Fri, Dec

Re: discuss nifi 0.4.1

Sean, Yeah i don't disagree with that point. The caveat being it was only a change to that client not a change to support the new client API and the behavior with existing clients old and new verified. I'd prefer to stick with 0.4.1 and if you still think it is best to actually just revert that

Re: discuss nifi 0.4.1

Can we update to 0.5.0 instead? The kafka client change isn't something I'd expect in a patch release. On Fri, Dec 18, 2015 at 9:54 PM, Joe Witt wrote: > ok - so master is presently on 041 and it does indeed appear to be all > incremental friendly fixes. So looks like we can just use the normal

Re: discuss nifi 0.4.1

ok - so master is presently on 041 and it does indeed appear to be all incremental friendly fixes. So looks like we can just use the normal process. As excited as I was to use cherry-pick doesn't look like it is needed. The bugs fixed on 041 so far are all nice cleanup items and things which hav

Re: Cluster Start Error: Apache NiFi is already running, listening to Bootstrap on port

got it. now my cluster is all set :) Thanks > On Dec 18, 2015, at 5:04 PM, Matt Gilman wrote: > > Sumo, > > It appears that while getting all the nodes stood up, there is no node that > is assigned the primary role. NiFi will be in safe mode until a primary is > established. If you go to the

Re: Cluster Start Error: Apache NiFi is already running, listening to Bootstrap on port

Sumo, It appears that while getting all the nodes stood up, there is no node that is assigned the primary role. NiFi will be in safe mode until a primary is established. If you go to the cluster table (accessed from the cluster icon in the upper right hand corner) you should be able to assign the

Re: Testing handling of static class methods

Definitely a topic ripe for debate :) In my view there’s a whole spectrum, with one side being the case Oleg describes, where the existing encapsulation is not compromised solely for the sake of testing. On the far side is pure design-by-contract. For example, the case could be made that the JMS

Re: Cluster Start Error: Apache NiFi is already running, listening to Bootstrap on port

Issue 1: in my NiFi installation I granted only read access to NIFI_HOME/lib and I got this error while trying to start NiFi. This got resolved when I gave read+write access to NIFI_HOME/lib. this makes me wonder why NiFi start process needs write access to lib folder! INFO [main] org.apache.ni

Re: Testing handling of static class methods

Personally I am with Joe on this one Exposing visibility on the method just for testing is very dangerous as it breaks encapsulation. There are different expectations and consideration on things that are made private, protected and public. Yes, all of that is meaningless when one uses reflectio

Re: Testing handling of static class methods

Wrapping createMessageProducer() in an instance method is a good suggestion, but it seems overkill just to enable testing. Prompted by Oleg's suggestion, I got around instance variable visibility with Reflection, which is nice because it doesn't require "private" be changed to "protected" in the c

Re: Testing handling of static class methods

If you get it into a protected instance method, you can also make an inner class in your test, something like TestablePutJMS extends PutJMS, and overrides that method to return a mock or whatever you want. That is a common pattern in a lot of the processor tests. On Fri, Dec 18, 2015 at 3:44 PM, M

Re: Testing Custom Validators

Thanks, I'm guessing that subject is not to0 important to the validation workflow but provides useful info for the user in the context of the property that they are setting. The validator I'm writing is not using the context so it should be fine. If I need to do more I guess I'll figure out how th

Re: Testing handling of static class methods

You could move the one static call into an instance method of PutJMS, and use Mockito.spy() to get a partial mock of the processor, then use when() to override the instance method in the test. Not sure if that's how it's done in other places but it's worked for me in the past. Regards, Matt Se

Testing handling of static class methods

For unit testing, one problem I've run into is overriding the returns from static class methods. For instance, PutJMS contains this code: try { > wrappedProducer = JmsFactory.createMessageProducer(context, true); > logger.info("Connected to JMS server {}", > new Object[]{conte

Testing Custom Validators

I'm trying to create some tests for some Validators that I'm creating. But I can't figure out an easy way to create MockValidationContext. I don't want to create the whole environment that I would for Processors. I looked at nifi/nifi-commons/nifi-processor-utilities/src/test/java/org/apache/nifi

Re: Cluster Setup

Thank you for your help. I deleted the flow.xml.gz . So now I have the NCM on machine 'b' and a node on machine 'c'. I start up a and then start up b. In b's logs I see logs of heartbeats: 2015-12-18 14:41:05,807 INFO [Process NCM Request-10] o.a.n.c.p.impl.SocketProtocolListener Finished proce

Re: Cluster Start Error: Apache NiFi is already running, listening to Bootstrap on port

Thanks Corey and Mark for quick response. You are right, I was sharing some folders using symbolic links between NCM and Node1. After removing sharing for bin folder, it works fine :) NCM/Node1 bin -> /software/nifi/latest/bin/ conf content_repository database_repository docs -> /software/nifi/

[GitHub] nifi pull request: NIFI-1300 - Penalize flowfiles when message sen...

Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/145#issuecomment-165876212 LGTM! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

Re: Cluster Start Error: Apache NiFi is already running, listening to Bootstrap on port

If you have a node and cluster on the same box you must be running on a different ports. Also, if you are not using the default locations of the repositories, you should set up the repos under different storage locations. For instance, on ours, the ncms, keep the default locations and the nodes are

Cluster Start Error: Apache NiFi is already running, listening to Bootstrap on port

Hi I am following clustering instructions as per the link below: NCM, Node1 in Server1 and Node2 on Server2. https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#clustering I created two copie

Re: Cluster Setup

Hello, You can run the NCM on the same machine as a node, but they still have to be two separate processes. You would create two copies of the directory where you extracted nifi and set one to be the manager and one to be the node, you'll also have to give them different nifi.web.http.port values.

Cluster Setup

Howdy, I'm trying to set up a cluster for the 1st time. I 1st tried to setup a NCM and a node on the same machine. In nifi.properties I set: nifi.web.http.port=8081 nifi.cluster.is.node=true nifi.cluster.node.address= nifi.cluster.node.protocol.port=8083 nifi.cluster.is.manager=true nifi.clust

Re: Support for Elastic Search in Future releases

Shweta, Please subscribe to the mailing list so that the community may continue to see your messages without requiring moderator support each time. Please use the subscribe link found here https://nifi.apache.org/mailing_lists.html Thanks Joe On Fri, Dec 18, 2015 at 2:17 AM, shweta wrote: > Hi

Re: Support for Elastic Search in Future releases

Shweta, I am also looking forward for ES support. In the mean time I inject data using PostHTTP processor and can try to help you if you have any questions. I even managed to create index-per-day because http processor URL property supports scripting language and I can format current date as a str

Re: Support for Elastic Search in Future releases

Shweta, There is a Jira case for Elasticsearch processors: https://issues.apache.org/jira/browse/NIFI-1275 I plan to work on these (with other folks in the NiFi community if interested) very soon. Regards, Matt On 12/18/15, 2:17 AM, "shweta" wrote: >Hi, > >I wanted to know if there are a

Support for Elastic Search in Future releases

Hi, I wanted to know if there are any plans to have custom processors supporting Data ingestion/egestion for Elastic search just like there is on for SOLR. Thanks, Shweta -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Support-for-Elastic-Search-in-Fut