Re: PutElasticsearch5 Processor Finished Processing

Thank Matt, I understand what you mean about NiFi being "flow" oriented and that is what the PutElasticsearch5 processor has been designed for. I agree with you that what I'm trying to do is batch oriented. I'm trying to avoid creating a custom processor for what I'm trying to do so I'll explain

Re: PutElasticsearch5 Processor Finished Processing

Leng, Generally, Apache NiFi is data "flow" oriented, in the same sense of a water flow (along pipes, for example) that might emit a lot or a little (or none) at any one time, but overall the water continues to flow through, and there might not be a discrete concept of "finished". In your case,

PutElasticsearch5 Processor Finished Processing

Hello, Is there any easy way to tell when the PutElasticsearch5 processor has finished inserting or updating records in the database? What I'm looking for is some way for the processor to signal that it has finished processing all the insert or updates so I know the database is in the correct

Re: Closing in on a NiFi 0.8.0 release?

All, I have started going through JIRA and identifying remaining issues against the 0.x branch to prepare for a release, and I've worked a couple of the JSON.org Cat-x license issues on that branch. I would like to volunteer to be release manager for a 0.7.3 release, if you will let me try. ;-)

Re: Documentation for 1.x

Tony, Per James' suggestion, I created NIFI-3701 to track documentation enhancement requests. I will update the ticket with more specifics. Thanks, Mark On Wed, Apr 12, 2017 at 12:04 PM, Tony Kurc wrote: > Mark, > The docs are community developed. The community would be

Re: nifi.templats.directory

Excellent! This is a perfect example of some of the "insider information" I'd like to see in the documentation. (See my other mailing list item.) I just tested it out and worked like a charm! Thanks for the insight. Mark On Wed, Apr 12, 2017 at 12:28 PM, Mark Payne wrote:

Re: Documentation for 1.x

Mark, The docs are community developed. The community would be very accepting of improvements and fixes. That being said, there is more documentation on how to contribute code than there is documentation, and it can depend if it is in confluence, the processors, or on the web page. Do you have

Re: Documentation for 1.x

Mark, Would you please open a JIRA ticket for known doc issues and feedback ( https://issues.apache.org/jira/browse/NIFI/)? I do not know if anyone is actively doing such a review at this minute, but the documentation is frequently updated as contributions come in. By the way, we are always

Documentation for 1.x

I have been asking many questions lately regarding NiFi 1.x because we are in the process of more deliberately evaluating 1.x as it relates to our current production level flows. In the process, I have found the documentation to be incomplete, sometimes incorrect (e.g. typo), contain references to

nifi.templats.directory

In NiFi 1.x (as compared to 0.x), any templates are now stored directly in the flow.xml.gz file. Is that correct? If so, what is the purpose (if any) of the nifi.properties entry for "nifi.templates.directory"? Should this property be deprecated/removed?

Re: Shutdown of one Node in Cluster

Excellent! Glad it's all working now. And thanks for the follow-up to let us know! -Mark > On Apr 12, 2017, at 11:30 AM, Mark Bean wrote: > > Mark, > > I believe you're right. Yesterday, I corrected a typo in the > nifi.properties file related to the FQDN name. I

Re: Shutdown of one Node in Cluster

Mark, I believe you're right. Yesterday, I corrected a typo in the nifi.properties file related to the FQDN name. I thought it was only the site-to-site property (nifi.remote.input.host). However, when I intentionally introduced a typo to one of the three ZK servers in the

Re: Shutdown of one Node in Cluster

Mark, I haven't seen this behavior personally, so I can't be sure why exactly it would change state to SUSPENDED and not then re-connect. In your nifi.properties, do you have the "nifi.zookeeper.connect.string" property setup to point to all 3 of the nodes, also? If so, it should be able to