Re: ListSFTP incoming relationship

Scott This idea has come up a couple of times and there is definitely something intriguing to it. Where I think this idea stalls out though is in implementation. While I agree that the other List* processors might similarly benefit lets focus on ListFile. Today you tell ListFile what directory

ListSFTP incoming relationship

Hello Devs, I would like to request a feature to a major processor, ListSFTP. But before I do down the official road, I wanted to ask if anyone thought it was a terrible idea or impossible, etc. The request is to add support for an incoming relationship to the ListSFTP processor specifically,

Re: Maven Build Failure

Aldrin, That Docker image worked great for 1.5.0. When I tried to run it with the latest master branch, however, I got the same error for nifi-slack-processors I mentioned previously. But after reading the response from Joe Percivall, which indicated that the slack processor step had a test

Apache NiFi 1.6.0 RC2 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file: gpg --import KEYS # [optional] Clear out local maven

[VOTE] Release Apache NiFi 1.6.0 (RC2)

Hello, I am pleased to be calling this vote for the source release of Apache NiFi nifi-1.6.0. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1123 The Git tag is nifi-1.6.0-RC2 The Git commit ID is

Re: Class Loading Conflicts - Different JAR Versions

Also, regarding the elastic search issue Mike mentioned… Usually when a processor can’t select the controller service at runtime it is because theres an issue with the way the dependencies are setup between NARs. There should generally be dependency paths like the following…

Re: Class Loading Conflicts - Different JAR Versions

I’m a +1 for moving the Mongo stuff out of standard services. Controller service APIs should always be broken out into their own NAR, but the processors and implementation can usually be bundled together. So something like the following would work: nifi-mongo-bundle -

Re: Class Loading Conflicts - Different JAR Versions

I was just following a convention at the time. So unless something breaks because of the move, I don't see any reason why it would be an issue to move it. In fact, with NIFI-4325 the only reason I put the new ElasticSearch service/api in the standard-services segment of the code base was I ran

Re: Class Loading Conflicts - Different JAR Versions

Brian (this one's all you ;), I think that PR is quite welcome in my opinion, but I'd like to get Mike Thomsen's and others' opinions on the subject too, I think Mike wrote the original service (or at the least is very knowledgable about Mongo and NiFi), he might have run into issues that led him

Re: Class Loading Conflicts - Different JAR Versions

Matt, +1 [non-binding] for the idea to move the Mongo dependencies into that bundle. I think it will likely need the NAR dependency on nifi-standard-services-api in order to provide a link to the SSL Context Service. Is that ticket / PR worthy as a one-off in the short term? No doubt the

RE: SOAP Service through InvokeHTTP

Mike is correct, Put your SOAP XML in the body (I use a ReplaceText Processor), add your Attributes to Send and then Invoke using the correct URL: Here is the SOAP section from one of my flows: Step 1) Replace Text Processor Search Value(?s)(^.*$) Replacement Value

Re: Class Loading Conflicts - Different JAR Versions

Bri/yan, IMO I think we'd be better off with moving the nifi-mongodb-client-service-api and nifi-mongodb-services bundles into the nifi-mongodb-bundle. That's something I missed while reviewing the PR that put them in standard services. I don't see a direct dependency on nifi-standard-services,

Re: Class Loading Conflicts - Different JAR Versions

Thanks, Bryan! Sure enough, we have nifi-standard-services-api-nar as a parent to use the standard SSLContextService. Sounds like upgrading the mongo-java-driver for the base build is the way to go for us. Thanks again, Brian On Mon, Mar 26, 2018 at 15:29 Bryan Bende wrote: >

Re: Class Loading Conflicts - Different JAR Versions

Brian, Is your custom processor using the MongoDBClientService provided by NiFI's standard services API? or does your NAR have a parent of nifi-standard-services-api-nar to use other services? Looking at where the Mongo JARs are from a build of master... find work/nar/ -name *mongo-java*.jar

Class Loading Conflicts - Different JAR Versions

Hey all, Is there a means of troubleshooting a custom NAR that seems to be having runtime conflicts by picking up an older JAR that's provided by the NiFi standard bundle? In this particular case, I'm using some custom processors that are built against NiFi 1.4.0 and have a dependency on MongoDB

Re: Maven Build Failure

I ran into the second error today after wiping my m2 directory and running a parallel build skipping tests. Looking at the maven pom, I believe it is because "nifi-slack-processors" has a test dependency on "nifi-standard-processors". If you build the "nifi-standard-processors" first, it should

Re: Weird issue w/ Redis pool service in an integration test

Ah yea, take a look at RedisDistributedMapCacheClientService, that one is closer to what you need. Something like RedisConnectionPool redisConnectionPool = context.getProperty(REDIS_CONNECTION_POOL).asControllerService(RedisConnectionPool.class); RedisConnection redisConnection =

Re: Weird issue w/ Redis pool service in an integration test

Yeah, it does. Copied withConnection from the state provider. Looks like copya pasta may have struck again... On Mon, Mar 26, 2018 at 11:44 AM, Bryan Bende wrote: > I can't tell for sure, but the stacktrace looks like your > AbstractRedisProcessor is making a direct call to

Re: published by PublishKafkaRecord_0_10 doesn't embed schema.

There are no community plans to do a 1.4.1 release at this time. Thanks On Mon, Mar 26, 2018 at 11:28 AM, Milan Das wrote: > Hi Bryan, > We are using NIFI 1.4.0. Can we backport this fix to NIFI 1.4? > > Thanks, > Milan Das > > On 3/26/18, 11:26 AM, "Bryan Bende"

Re: published by PublishKafkaRecord_0_10 doesn't embed schema.

You might be able to get the nifi-kafka-0-10-nar from 1.5.0 and run it in 1.4.0. On Mon, Mar 26, 2018 at 11:28 AM, Milan Das wrote: > Hi Bryan, > We are using NIFI 1.4.0. Can we backport this fix to NIFI 1.4? > > Thanks, > Milan Das > > On 3/26/18, 11:26 AM, "Bryan Bende"

Re: Weird issue w/ Redis pool service in an integration test

https://github.com/MikeThomsen/nifi/commit/dad71af803a9ead5bcbead3ce65671c4c2430605#diff-09d6acf9b469f7d2491ab7dbdab93fea On Mon, Mar 26, 2018 at 11:38 AM, Bryan Bende wrote: > Can you share the code for your AbstractRedisProcessor? > > > On Mon, Mar 26, 2018 at 9:52 AM, Mike

Re: Weird issue w/ Redis pool service in an integration test

I can't tell for sure, but the stacktrace looks like your AbstractRedisProcessor is making a direct call to RedisUtils to create a connection, rather than using the RedisConnectionPool to obtain a connection. On Mon, Mar 26, 2018 at 11:38 AM, Bryan Bende wrote: > Can you share

Re: Weird issue w/ Redis pool service in an integration test

Can you share the code for your AbstractRedisProcessor? On Mon, Mar 26, 2018 at 9:52 AM, Mike Thomsen wrote: > Over the weekend I started playing around with a new processor called > PutRedisHash based on a request from the user list. I set up a really > simple IT and

Re: published by PublishKafkaRecord_0_10 doesn't embed schema.

Hi Bryan, We are using NIFI 1.4.0. Can we backport this fix to NIFI 1.4? Thanks, Milan Das On 3/26/18, 11:26 AM, "Bryan Bende" wrote: Hello, What version of NiFi are you using? This should be fixed in 1.5.0:

Re: Objection: LDAP Auth needs HTTPS

Hello, Passing LDAP credentials in plain-text over http would not be secure. You'll want to have the SSL connection pass through the load balancer all the way to the NiFi nodes. There are several articles on setting up a secure NiFi cluster:

Re: published by PublishKafkaRecord_0_10 doesn't embed schema.

Milan, What version of NiFi are you running? This sounds like NIFI-4639 [1], which was resolved in version 1.5.0. Thanks -Mark [1] https://issues.apache.org/jira/browse/NIFI-4639 On Mar 25, 2018, at 6:45 PM, Milan Das > wrote: Hello Nifi Users,

Weird issue w/ Redis pool service in an integration test

Over the weekend I started playing around with a new processor called PutRedisHash based on a request from the user list. I set up a really simple IT and hit a problem pretty quickly. This passes validation: @Test public void testStandalone() throws Exception { final String attrName =

Re: published by PublishKafkaRecord_0_10 doesn't embed schema.

Hello, What version of NiFi are you using? This should be fixed in 1.5.0: https://issues.apache.org/jira/browse/NIFI-4639 Thanks, Bryan On Sun, Mar 25, 2018 at 6:45 PM, Milan Das wrote: > Hello Nifi Users, > > Apparently, it seems like PublishKafkaRecord_0_10 doesn't

Re: while viewing Data provenance

Hello The image did not come through. Can you please find some logs/stacktraces and share the text of that. Probably best to create a JIRA. The current default provenance repository was rewritten due to some performance issues. You can switch to the newer, far faster, and as many have found

Re: [EXT] Re: NiFi Versioned Process Group Status Icons

I would factor in any plans for a local version history, it may add new requirements to this status icon. Just saying there's more to that logic potentially. Andrew On Sun, Mar 25, 2018, 10:17 PM Peter Wicks (pwicks) wrote: > Matt, > > If you really want to enable awareness

while viewing Data provenance

Hi, while trying to view data provenance,it is displaying as /home/username/nifi-1.4.0/provenance_repository/index-1520839014000/_5j_Lucene41_0.doc. i didn't get what it is,so i checked in that folder but i didn't see that file _5j_Lucene41_0.doc.you can see below image how it is

Re: [CANCEL][VOTE] Release Apache NiFi 1.6.0 RC1

Hi, I didn't do a "proper" review, but I built the PR and it does fix the issue on my side. Pierre Le dim. 25 mars 2018 à 18:21, Bryan Bende a écrit : > I plan to review/test the fix that Sivaprasanna made first thing tomorrow > morning, unless someone gets to it before