Re: Approaches to Array in Json with Nifi?

Sorry, Aldrin. I forgot to answer your question. My arrays do not share fixed number of values. Thanks. Hong *Hong Li* *Centric Consulting* *In Balance* (888) 781-7567 office (614) 296-7644 mobile www.centricconsulting.com | @Centric On Wed, Apr 6, 2016 at

Re: Few doubts about NiFi cluster

Hi Sudeep, Answers to your questions: 1) In a clustered environment, each processor will have the same configuration the flows are identical across each node in the flow with the NCM establishing mutations across each instance via a two-phase commit. Through the mentioned scheduling strategy,

Re: nifi.content.repository.archive.max.retention.period

Andre, Sorry this got lost in the mail pile. Your assumptions are correct and that is the anticipated behavior. Has this been a reproducible and/or persistent issue (the lack of archiving causes disk consumption to grow unbounded)? If so, any level of context you can provide to the flow such

Re: custom processor development : problems with scops in parent POM

Hello! Are you trying to incorporate this into the repository check out or a standalone bundle? In the case of the latter, could you confirm you have established a project dependency structure such as that outlined in the Wiki [1]? Not only is a provided scope needed to be able to

Re: Approaches to Array in Json with Nifi?

​Does it store as an attribute if you change the return type from auto-detect to JSON ? *Return Type* auto-detect - auto-detect - json - scalar Indicates the desired return type of the JSON Path expressions. Selecting 'auto-detect' will set the return type to 'json' for a Destination

Re: Approaches to Array in Json with Nifi?

The issue I run into there is when I specify under EvaluationJsonPath, firstRateValue = $.rate[0] $.rate[0] is a scalar value that is assigned to the processor property firstRateValue, which is also a scalar. But $.rate[*] is an array or vector. Nifi will send error there and the process will

Re: problem with putElasticsearch processor

Hey Philippe Couple of things we can do to see what might be going on. 1. Check the port being used by put elastic search. Port 9200 is usually the default http port and 9300 is the default transport port. In put elastic search we need to use the transport port. 2. If the port is correct try

Approaches to Array in Json with Nifi?

Let's say we have object and array in Json as {"company":"xyz", "rate":[0.02, 0.03, 0.04]} With Nifi processor EvaluateJsonPath, we may get the individual values of the object and array such as companyValue = $.company firstRateValue = $.rate[0] What would you recommend if I need to capture

Re: putKafka processor with Avro Format

I see the patch in Jira. You confirm that avro format is supported for putKafka and getKafka processor ? Thanks Ali On Wed, Apr 6, 2016 at 4:14 PM, Joe Witt wrote: > Ali > > It is very possible you're being bitten by a bug we have with > PutKafka. It is fixed in this branch

Re: putKafka processor with Avro Format

Ali - I can confirm that all formats are supported for Put/Get Kafka processors. The interaction with Kafka as far as the messages are concerned is just 'bytes'. The reason it isn't working well is due to the bug I'm mentioning and that is a NiFi bug (not Kafka). It is fixed and we'll have a

putKafka processor with Avro Format

Hi, I'm exploring integration possibility of nifi processors with kafka. I use PutKafka to puch avro generated flow from ExecuteSQL. I verify that the topic created in Kafka is alimented with data using kafka-console-consumer bash command. Then I try to use getKafka processor to pull all the