Re: PutElasticSearchRecord

Juan, Yes the current behavior is to move the entire input flowfile to failure if any errors occur. Some other record-aware processors create separate flow files for failed and successful records, but PutElasticsearchHttpRecord does not (yet) do that. Please feel free to write a Jira for this

Re: Default scheduling

Pierre, Anyway to reconcile the annotation declaration with the variable registry on the instance? That way a reasonable default could be declared in the annotation, but it could also be overridden by a configured value in the running NiFi instance. For example, I like my GenerateFlowFile

Re: problem with Nifi / Atlas integration - has anyone some experience with this integration ?

Hi Dominique, Thank you for your interest in NiFI and Atlas integration. I have some experience with that, and actually written the NiFi reporting task. I have two things in mind could be related to your situation. One is NIFI-4971, it's under being reviewed now. It fixes lineage reporting issue

Re: PutHDFS how to use a remote HDFS

The files don't necessarily need to be on the NiFi classpath, but they do need to be on the local file system of NiFi. You can set the Hadoop Configuration Resources properties of the PutHDFS processor to a comma-separated list of the paths for core-site.xml and hdfs-site.xml. As far as I know,

Re: Default scheduling

+1 on this idea. We were considering doing this as well as we have ran into issues with the system getting borked because of users unknowingly doing the same with items such as GenerateFlowFile and some others. I think its a great idea! Cheers, Ryan H On Thu, Apr 26, 2018 at 8:14 AM, Pierre

Re: Default scheduling

Actually the InvokeHTTP is a special case because it can accept incoming relationship... so setting a default like 1s could be unwanted for some users... but I think it'd be less risky to have a default of 1s that people can change rather than keeping 0s as default and having the risk of harming

Re: Default scheduling

Looks like a great idea to me as well. //Jorge From: Otto Fowler Sent: Thursday, April 26, 2018 12:55:47 PM To: Pierre Villard; users@nifi.apache.org Subject: Re: Default scheduling I think this is a great idea. I have done this

Re: Default scheduling

I think this is a great idea. I have done this myself with a ‘metered’ api using the AWS Web Gateway Api version of InvokeHttp ( https://github.com/apache/nifi/pull/2588 shameless plug ). I can’t think of how 0s would ever be a sane default. On April 26, 2018 at 04:18:04, Pierre Villard

problem with Nifi / Atlas integration - has anyone some experience with this integration ?

Hi, I have defined a simple pipeline in Nifi: GetFile => some processor doing a dummy transformation => PublishInKafka ...with Atlas integration for lineage purposes Versions: -- Atlas 0.8.0 (Stack : HDP 2.6.4) -- Nifi 1.5.0 and I have put some (dummy) file into the input

Default scheduling

Hi there, Since few versions already, it's now possible to define default values for scheduling of the components using a dedicated annotation. Example @DefaultSchedule(strategy = SchedulingStrategy.TIMER_DRIVEN, period = "1 min") I'm wondering if the community would be OK about setting a