Re: Creating a custom DatabaseAdapter

Stanislav, This is not your fault, it is a current limitation due to the organization of the NiFi submodules with respect to the location of DatabaseAdapter. In general, when a NiFi interface is to be extensible, there is a submodule for the API JAR to be available to other NARs/submodules/etc.

Re: [VOTE] Release Apache NiFi 1.1.2

+1 - release On Fri, Feb 17, 2017 at 2:37 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.1.2. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/o

Re: Sensitive-value properties

A lot of this specific information is buried in the Admin Guide, but I agree with your thoughts in general. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Feb 17, 2017, at 2:36 PM, Russell Bateman wrote: >

Re: Sensitive-value properties

I thank all of you for this exhaustive treatment. Sometimes I regret that what flies around in forum threads never makes it into the docs. On 02/17/2017 02:32 PM, Andy LoPresto wrote: Russ, Both Bryan and Joe are exactly correct in their responses. To add some context, each sensitive property

Re: Sensitive-value properties

Russ, Both Bryan and Joe are exactly correct in their responses. To add some context, each sensitive property value is encrypted using the specified algorithm in nifi.properties. By default, and therefore on any unmodified system, this is PBEWITHMD5AND256BITAES-CBC-OPENSSL, which means that the

Re: [VOTE] Release Apache NiFi 1.1.2

+1, binding Comments: * The hash provided in the email is for the next development version, 1.1.3-SNAPSHOT. The hash for 1.1.2, and correctly tagged as such, is e31088642b6fdc7cafb52208a6ba29216dde7898 [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=e31088642b6fdc7cafb52208a6ba292

Re: [VOTE] Release Apache NiFi 1.1.2

Aldrin noted the tag was not pushed. It is present now: nifi-1.1.2-RC1: https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=e31088642b6fdc7cafb52208a6ba29216dde7898 Andy LoPresto

Re: [VOTE] Release Apache NiFi 0.7.2

Thanks to Aldrin for pointing out that the tags did not get pushed for some reason. They are both present now: nifi-0.7.2-RC1: https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=6435063885ceb447de89683c0a9149f782112785

Re: [VOTE] Release Apache NiFi 0.7.2

+1, binding Comments: * Hashes and signature looks good * Build and basic flows worked * 0.7.2-RC1 tag is currently absent on the Apache repository On Fri, Feb 17, 2017 at 2:51 PM, Matt Gilman wrote: > +1 (binding) Release this package as nifi-0.7.2 > > On Thu, Feb 16, 2017 at 11:42 PM, Andy L

Re: [VOTE] Release Apache NiFi 0.7.2

+1 (binding) Release this package as nifi-0.7.2 On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-0.7.2. > > The source zip, including signatures, digests, etc. can be found at: > https://reposito

Re: Sensitive-value properties

Russell, Sensitive property values are stored in the flow.xml.gz in encrypted form. The encryption is based on the value of nifi.sensitive.props.key= and if you haven't set one there is a default in the code. If you have the same sensitive properties key in both instances than you can copy the flo

Re: Sensitive-value properties

Russ, The values are stored within the flow.xml.gz and are encrypted. They are encrypted/decrypted by the core framework outside the control of any extension code. Their values are not returned again to the client side in encrypted form or otherwise. The flow.xml.gz can be copied to another nif

Sensitive-value properties

1. Where are the values of sensitive-value properties stored? 2. How do they work? (if not obvious from #1) 3. Can /flow.xml.g//z/ be copied wholesale or in part to another instance of NiFi? Thanks, Russ

Re: [VOTE] Release Apache NiFi 0.7.2

+1 (binding) Release this package as nifi-0.7.2 On Fri, Feb 17, 2017 at 12:55 PM, Joe Witt wrote: > Mike, > > You're absolutely right that there are some good fixes to be included > in an upcoming release. There is no reason someone couldn't put > together an 0.7.3. > > This is just something th

Re: [VOTE] Release Apache NiFi 1.1.2

+1 (binding) Release this package as nifi-1.1.2 On Thu, Feb 16, 2017 at 10:37 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.1.2. > > The source zip, including signatures, digests, etc. can be found at: > https://reposito

Re: [VOTE] Release Apache NiFi 0.7.2

Mike, You're absolutely right that there are some good fixes to be included in an upcoming release. There is no reason someone couldn't put together an 0.7.3. This is just something that we're wanting resolved and have the energy to push forward and doesn't require additional testing as inclusio

Re: [VOTE] Release Apache NiFi 0.7.2

I'm sad that 0.7.2 does not contain some of the other bug fixes currently on the 0.x branch. It doesn't seem like it would have cost very much to just include them. +0 (non binding) -- Mike On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vo

Re: [VOTE] Release Apache NiFi 1.1.2

+1 (binding) Release this package as nifi-1.1.2 On Thu, Feb 16, 2017 at 10:37 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.1.2. > > The source zip, including signatures, digests, etc. can be found at: > https://reposito

Re: NiFi PutElasticsearch Processor

Shankha, With Java Regex'es, by default, the dot-character does not match newlines. So (.+) will only match a single line. On Extract Text, you can change the property named "Enable DOTALL Mode" to true, which should allow the .+ to capture all of the text in the FlowFile. Thanks -Mark > On

Creating a custom DatabaseAdapter

Hi, I would like to create a custom org.apache.nifi.processors.standard.db.DatabaseAdapter, is this possible? I have tried creating new class that implements the interface and specified the full class name in META-INF\services\org.apache.nifi.processors.standard.db.DatabaseAdapter file, and cr

Re: Query on nifi project deployment

Just to add some content here (was trying to find another thread discussing the same subject... but my search skills are low today...): if you want to deploy NiFi in a custom web application server, the first place I'd look at would be the nifi-runtime project and in particular at this place: http

Re: Query on nifi project deployment

Hi, NiFi is running in its own embedded Jetty server. There is no way, at the moment, to allow NiFi deployment in other web application server. Hope this helps, Pierre 2017-02-17 13:55 GMT+01:00 Deepak Kumar Patel : > Hi Dev Team, > > Can you guide me, I want to deploy the nifi project inJBoss

Query on nifi project deployment

Hi Dev Team, Can you guide me, I want to deploy the nifi project inJBoss/WildFly 10. Is It possible ? If possible, can you please share the steps. Thanks in Advance. Deepak Patel

travis-ci auto cancellation

dev, Would you mind if I configured the NiFi, MiNiFi and MiNiFI-CPP travis-ci integration to perform auto-cancellation when new commits are pushed to the same branch or PR? This should significantly reduce the number of builds we do per busy days and offer benefits to the whole community. Cheers

Re: Creating a custom DatabaseAdapter

Stanislav Sorry to hear you’re having problems. Is ether any way we can look at the code (i.e., via GitHub)? Also, when you say you don’t see your DatabaseAdapter is not picked up, do you see any messages in the logs? It is hard to determine the issue without more info, but usually symptoms li

Re: NiFi PutElasticsearch Processor

Hi, I have added ExtractText processor and there added a new property called myAttribute with value (.+). Then added AttributesToJSON processor with Attributes List as myAttribute. As result I am getting the below json structure. {"myAttribute":"test elasticsearch"} But it's not working for mult