Russell,
No worries. The Javascript application that runs the UI is simply invoking Ajax
(Asynchronous Javascript and XML) requests to normal HTTP endpoints provided by
the embedded Jetty server in NiFi. You don’t need to understand anything about
front-end development to monitor these requests
(Make that "not much of a web page developer". I'm a back-end Java guy
mostly, don't much value my UI skills and so have stayed away from the
browser except for straight HTML and CSS.)
On Fri, Jul 8, 2016 at 8:39 PM, Russell Bateman <
russell.bate...@perfectsearchcorp.com> wrote:
> Thanks, Andy a
Thanks, Andy and Matt, I had actually tried out the Developer Tools earlier
today as suggested by the doc,but, I'm not much of a web developer, don't
have a lot of familiarity with those tools in Chrome or in Firefox, and I
couldn't see anything going on (in Firefox) that was helpful. I may have to
Russell,
To echo Matt’s point, the NiFi UI uses the REST API on every command, and
developer tools is a great way to observe this.
Another example using the REST API is Andrew Grande’s “nifi-deploy-api” project
on GitHub [1]. It is a groovy script that can automate the deployment of NiFi
insta
Russell,
I can provide a more detailed response when I'm back in front of my computer
but thought I'd offer this as a quick suggestion.
All flows use process groups. The blank canvas when you load your nifi instance
is the root level process group. If you don't know the actual ID, you can use
Ah, for (9), I used system-diagnostics. (I had not spelled it correctly
when trying it before.)
On Fri, Jul 8, 2016 at 3:35 PM, Russell Bateman <
russell.bate...@perfectsearchcorp.com> wrote:
> I'm trying to figure out how to use the ReST (nifi-api) interface to
> accomplish a number of things. F
I'm trying to figure out how to use the ReST (nifi-api) interface to
accomplish a number of things. First, I've played successfully with it
doing simple things like getting configuration, a list of existing
processors, and the like. I've even discovered that in
controller/history/processors/{proces
And since i originally replied to the helper thread instead of the VOTE
thread...
+1 (binding)
Verified signature and checksums. Build completed without issue. Was able to
use the minifi-toolkit to convert
a nifi template and run it without any problem. All worked perfectly! Great
job, guys!
+1 (binding)
Verified signature and checksums. Build completed without issue. Was able to
use the minifi-toolkit to convert
a nifi template and run it without any problem. All worked perfectly! Great
job, guys!
> On Jul 6, 2016, at 10:29 PM, Aldrin Piri wrote:
>
> Hello Apache NiFi community,
+1, binding
Build, contrib, and associated documentation looks good.
Hashes and signatures check out.
Was able to use the generated assemblies to perform some tests and
communicate with a NiFi instance.
---
Folks,
Thanks for all the feedback. I've created tickets to capture all of the
points
My +1 vote from the other day is now binding.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jul 8, 2016, at 9:12 AM, Joe Witt wrote:
>
> +1 binding.
>
> Ran through full build verification. Check licensin
+1 binding.
Ran through full build verification. Check licensing/notice items and
hoping we can make that leaner and meaner over time as well.
Was able to use the toolkit to convert a nifi template to a minifi
config and fire that up and immediately see desired results.
Some feedback items.
1)
Team,
Here is a draft of what I plan to submit to the ASF board for our
quarterly report. Please review and provide feedback on anything you
think needs adding or clarified.
awesome to see how our community is growing!
Will submit in a day or so.
Thanks
Joe
## Description:
- Apache
+1 (non-binding)
Downloaded RC, verified checksums, gpg.
Built with contrib-check turned on.
Ran through all templates at
https://github.com/brosander/minifi-testkit/tree/8a8b9791a6b3d6404d6eaa6be48951851d3fa898/templates
(ran config.sh transform on each template to generate yaml, ran MiNiFi wit
Pradeep,
We are using the the Ganglia reporting task with the ELK stack to monitor our
NiFis. The reporting task sends metrics to a LogStash running a ganglia
plugin. We use Kibana to visualize the metrics and Watcher to create
notifications. It was fairly easy to setup and works quite well
+1 (binding)
Ran through the helper and verified functionality.
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com
On Thursday, July 7, 2016 2:13 PM, Joe Percivall
wrote:
Vote forth-coming but regarding Andy's notes/questions:
I agree with using HTTPS links
Andre,
Currently each processor can only persist one state map. The reason for
this is that behind the scenes it is storing the state under a key like
"components/" to ensure that the state is only for that
processor, and can't be messed with by other processors.
I supposes we could still have a w
Jira link
https://issues.apache.org/jira/browse/NIFI-2200
Thanks.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/QueryDatabaseTable-tp12698p12717.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
all,
I ended up doing a fork TailFile and bolting together a frankenprototype of
the processor here:
(apologies for the spaghettiness of the code but the task was clearly
beyond my league... :-D )
https://github.com/trixpan/nifi/tree/NIFI-1170
I am still going through the basics of it but I woul
Congrats Andy!!!
On Thursday, July 7, 2016, Tony Kurc wrote:
> Glad to have you aboard, Andy!
>
> On Thu, Jul 7, 2016 at 12:44 PM, Joe Witt > wrote:
>
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > Andy LoPresto has accepted the PMC's invitation to join the Apache
20 matches
Mail list logo