Re: [ANNOUNCE] New Apache NiFi Committer Sivaprasanna Sethuraman

Congrats ! Jorge > On 6 Jun 2018, at 18:44, Otto Fowler wrote: > > Congratulations! > > > On June 5, 2018 at 10:09:28, Tony Kurc (tk...@apache.org) wrote: > > On behalf of the Apache NiFI PMC, I am very pleased to announce that > Sivaprasanna has accepted the PMC's invitation to become

Re: KerberosProperties.validatePrincipalAndKeytab Error ?

Ok that makes sinn. It was really confusing because all other processors when they say Supports language expression it works on the incoming flow files. Thanks for the heads up. Jorge Machado > On 4 Jun 2018, at 14:34, Mark Payne wrote: > > Jorge, > > These properties do sup

Re: KerberosProperties.validatePrincipalAndKeytab Error ?

Sivaprasanna, Yes I have that property set, the Unit test is failing IMHO it should not. Jorge Machado Best Regards > On 4 Jun 2018, at 12:09, Sivaprasanna wrote: > > Jorge, > > Both 'Kerberos Principal' abd 'Kerberos Keytab' support NiFi expression > language so ${princ

Re: Disable all Remote Processors

missing something? > > Pierre > > 2018-05-15 9:23 GMT+02:00 Jorge Machado : > >> hi all, >> >> it should be possible to disable all remote processors groups inside a >> Processor group right ? >> should we start with a PR for the API ? >> >> Jorge Machado >> >> >> >> >> >> >>

Disable all Remote Processors

hi all, it should be possible to disable all remote processors groups inside a Processor group right ? should we start with a PR for the API ? Jorge Machado

Pushing flows to Registry with Sensitive Information

Hi Guys, so I was playing with the registry and If I pushed a Processor that has sensitive information like a password it will be discarded when pulling it from the Registry, which is fine. Now comes the but. But if I put a variable there IMHO I think it should save it on the registry. What

Nifi UI improvement

Hi guys, Is there any effort to improve the UI ? One nice feature to have would be: Have the possibility to limit searches on a canvas. Let’s say we are inside a processor group and we only want to search from there on. Regards Jorge Machado

Re: FlattenJson

to Flowfile. Would be the Changed accepted ? I would create a PR for it. Jorge Machado > On 20 Mar 2018, at 22:35, Otto Fowler <ottobackwa...@gmail.com> wrote: > > We could start with routeOnJsonPath and do the record path as the need > arises? > > > On March

Re: Stackoverflow question: Moving data from one RDB to another through NiFi

That would be probably the fastest way. Jorge Machado www.jmachado.me > On 22 Mar 2018, at 08:38, Brett Ryan <brett.r...@gmail.com> wrote: > > Hmmm, now I’m doubting myself. It’s possible we sqoop to hdfs then sqoop > out, will have to look, sorry if I am wrong. >

Re: Stackoverflow question: Moving data from one RDB to another through NiFi

you copy the files into the server and on the server then use some import bulk….. Jorge Machado > On 22 Mar 2018, at 08:13, Brett Ryan <brett.r...@gmail.com> wrote: > > Could Sqoop [1] be an option? > > [1]: http://sqoop.apache.org/ > >> On 22 Ma

Re: FlattenJson

So that is what we actually are doing EvaluateJsonPath the problem with that is, that is hard to build something generic if we need to specify each property by his name, that’s why this idea. Should I make a PR for this or is this to business specific ? Jorge Machado > On 20 Mar 2

Re: FlattenJson

From there on we use a lot of routeOnAttritutes and use that values on sql queries to other tables like select * from someTable where id=${myExtractedAttribute} To be honest I tryed JoltTransformJSON but I could not get it working :) Jorge Machado > On 20 Mar 2018, at 15:12, Matt Burg

Re: FlattenJson

;){ attrs[k] = v.toString() } } } as InputStreamCallback) flowFile = session.putAllAttributes(flowFile, attrs) session.transfer(flowFile, REL_SUCCESS) some code removed Jorge Machado > On 20 Mar 2018, at 15:03, Bryan Bende <bbe...@gmail.com> wrote: > > Ok it is still

Re: FlattenJson

to use this standard processor and instead of writing this to a flow content write it to attributes. Jorge Machado > On 20 Mar 2018, at 14:47, Bryan Bende <bbe...@gmail.com> wrote: > > What would be the main use case for wanting all the flattened values > in attributes?

Re: FlattenJson

Hi Pierre, I’m aware of that. So This means the change would not be accepted correct ? Regards Jorge Machado > On 20 Mar 2018, at 09:54, Pierre Villard <pierre.villard...@gmail.com> wrote: > > Hi Jorge, > > I think this should be carefully docum

FlattenJson

Hey guys, I would like to change the FlattenJson Procerssor to be possible to Flatten to the attributes instead of Only to content. Is this a good Idea ? would the PR be accepted ? Cheers Jorge Machado