Re: Identifier Attribute for PutElasticSearch

Hi Bryan, thank you so much for this. Once again, your replies are very valuable to me, it does now make more sense. Thank you -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Identifier-Attribute-for-PutElasticSearch-tp9683p9710.html Sent from the Apache

[GitHub] nifi pull request: NIFI-1816 Added provenance event SEND in Handle...

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/389#discussion_r61540826 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpResponse.java --- @@

Nifi failing to load - Unable to start flow controller?

My nifi was running fine the past week. I restarted the computer and needed to reboot nifi, but now nothing will load. I am unsure as to why this is happening and how to fix it. ERROR [NiFi logging handler] org.apache.nifi.StdErr Failed to start web server: Unable to start Flow Controller. What

Re: NiFi Script Tester utility

Matt, That's very cool. When I get some time I might try the script processor just to check the tester out. Joe On Thu, Apr 28, 2016 at 2:42 PM, Matt Burgess wrote: > I've been getting lots of questions about how to develop/debug scripts > that go into ExecuteScript.

Re: Nifi failing to load - Unable to start flow controller?

There should be more details in the nifi-app.log about why it failed to start. Typically it's accompanied with a stack trace detailing the issue. Do you see anything else? Matt On Fri, Apr 29, 2016 at 6:32 AM, mfzeidan wrote: > > My nifi was running fine the past

Re: GetKafka blowing up with assertion error in Kafka client code

I’ve created a JIRA[1] for this. Chris [1] https://issues.apache.org/jira/browse/NIFI-1827 On 4/28/16, 1:36 PM, "Oleg Zhurakousky" wrote: >Chris > >Thanks for looking into this and describing the problem. Indeed we have seen >similar symptoms but would

Re: Nifi failing to load - Unable to start flow controller?

Mark, You should be able to look at the $NIFI_HOME/logs/nifi-app.log file to determine what's going on. There should be a stack trace that provides a good bit of info. If you look at the log file, and it is not clear what is going on, please provide the stack trace so that we can help. Thanks!

Re: Nifi failing to load - Unable to start flow controller?

Here is the error coming from the FlowController: org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller. at org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:99) ~[na:na] at

[GitHub] nifi-site pull request: NIFI-1819 MINIFI-31 Providing initial inte...

GitHub user apiri opened a pull request: https://github.com/apache/nifi-site/pull/2 NIFI-1819 MINIFI-31 Providing initial integration of MiNiFi site resources. NIFI-1819 MINIFI-31 Providing an initial incorporation of MiNiFi site content within the nifi site. Performed

Re: Identifier Attribute for PutElasticSearch

Identifier Attribute is a little confusing and different, I struggled to decide whether to have an "Identifier" property or an "Identifier Attribute" property, and chose the latter because if you had an Identifier property and didn't use expression language, then the processor would immediately

Re: Testing processor from UI

Absolutely a great idea. With the feature proposal for interactive queue management which has some parts done one of the things desired was the ability to upload flowfiles directly to a given queue. It would be helpful then too to make it really easy to author/paste in attributes/content as you

FetchFile Cannot Allocate Enough Memory

I have been trying to run my data flow and I have been running into a problem with being unable to read FetchFiles. I will detail my process below and I would like some confirmation of my suspicions. First I am ingesting an initial file that is fairly large, which contains the path/filename of a

Re: FetchFile Cannot Allocate Enough Memory

Some googling of "FileNotFoundException cannot allocate memory" indicates that this is fairly common when running in a VM that has very little RAM, as there is not enough heap space even to create a linux process. Do you have a reasonable amount of RAM free on the box? Thanks -Mark > On Apr

Re: Nifi failing to load - Unable to start flow controller?

Mark, Did you by chance run out of disk space for your provenance repository? It it complaining that the Provenance repo has some invalid/corrupt files. You should be able to remove the files in the provenance_repository/journals/ directory and that should get you up & running, but it would

Re: FetchFile Cannot Allocate Enough Memory

Dale, I haven't seen this issue personally. I don't believe it has to do with content/flowfile repo space. Can you check the logs/nifi-app.log file and give us the exact error message from the logs, with the stack trace if it is provided? Thanks -Mark > On Apr 29, 2016, at 9:12 AM,

Re: FetchFile Cannot Allocate Enough Memory

Mark Payne wrote > Dale, > > I haven't seen this issue personally. I don't believe it has to do with > content/flowfile > repo space. Can you check the logs/nifi-app.log file and give us the exact > error message > from the logs, with the stack trace if it is provided? > > Thanks > -Mark Sure,

[GitHub] nifi pull request: [NIFI-1782] update toolbox, new global menu, an...

GitHub user scottyaslan opened a pull request: https://github.com/apache/nifi/pull/395 [NIFI-1782] update toolbox, new global menu, and new pallattes You can merge this pull request into a Git repository by running: $ git pull https://github.com/scottyaslan/nifi

Re: [jira] [Commented] (MINIFI-32) Design logo for MiNiFi

Wow, I hadn't noticed that but you are right. Though the documentation and most text uses "NiFi", the graphics are "nifi". I like the graphic, the rings of blocks around the drop instead blocks inside the drop make me think transport instead of processing, so that's great. On Fri, Apr 29, 2016

Re: PutSyslog IP Address

Hi Ronnie, syslog.sender is a NiFi specific attribute that is populated by ListenSyslog with the host/ip that created the connection to NiFi, it is not specific to syslog itself. syslog.hostname is the host that produced the actual log message and was parsed out from the syslog message, this

[GitHub] nifi pull request: NIFI-1554: Introduction of access controls on c...

Github user bbende commented on the pull request: https://github.com/apache/nifi/pull/393#issuecomment-215872920 I'm a +1... reviewed and looks good, ran the application in secure and un-secure modes to verify functionality, passes contrib-check. --- If your project is set up for