.
Thanks,
Bryan Rosander
On Tue, Jun 7, 2016 at 3:05 PM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Personally I am ok either way, however the question I have is consistency
> and how different artifacts written via html will be different
> (look-and-feel) from t
additionalDetails.md (and others) into an
equivalent html page.
Thanks,
Bryan Rosander
Hey all,
The pentaho-hdfs-vfs artifact is in the process of being deprecated and
superceded by vfs providers in their big data plugin.
They wouldn't be sufficient for outside use either way as they depend on the
big data plugin, Kettle, and the correct shim (see Matt's comment) to work.
A
danbr...@gmail.com> wrote:
> >> > +1
> >> >
> >> > On Wed, Jun 8, 2016 at 7:05 AM Andre <andre-li...@fucs.org> wrote:
> >> >
> >> >> +1 on this + a template that matches existing additional.html
> >> >
(which in small deployments that MiNiFi targets shouldn't be a
> problem) but makes it more user friendly. Enforcing uniqueness was added as
> part of a contribution from Bryan Rosander as a validation check when
> transforming the config.yml and applies to processors, connections, and
&g
. Might need to call it out
> > >> more or provide a more prescriptive pointer to how to build it, find
> > >> it, use it.
> > >>
> > >> 2) minifi-toolkit execution
> > >>
> > >> When running config.sh it say
Hi Andre,
I found a superuser answer that seems like it might be helpful in forcing
Outlook to use TNEF.
http://superuser.com/questions/613014/how-do-i-force-outlook-to-send-an-email-message-to-have-a-winmail-dat-attachment#answer-638244
Hope that helps.
Thanks,
Bryan
On Tue, Aug 9, 2016 at
Hey Steve,
That looks really cool! I cloned the git repo for the processors and
everything looks pretty standard. I was impressed with how concise your api
is, those concrete impls for parse and unparse took very little code :).
Pulled down daffodil source and built it (my first experience with
Hey Morgan,
As far as documentation on the yml schema, we've attempted to document both
its current state as well as the changes over time. [1]
In terms of converting the yml into a flow.xml (and nifi.properties), that
is done by the ConfigTransformer. [2] I wouldn't think it would be very
Hi Jochen,
I'm sorry that you had trouble with the cron documentation. Under the
covers we use Quartz to handle the cron scheduling. You can find a more
in-depth description of the cron string in their documentation. [1]
Year is an optional field and seems to be absent from the default.
1 is
Hey Matt,
If you don't want to use certificate authentication with the secured NiFi
instance, you could point it at an LDAP [1] server and then use a
username/password login to NiFi.
NiFi's processors can do everything from manipulating the filesystem of the
machine it is running on to dropping
+1 (non-binding)
Verified signature, checksums
Contrib check build with Oracle jdk 1.8.0_121 on Ubuntu, fresh local repo
Tested non-secured cluster with simple flow
Tested secured cluster with simple flow, command line site to site client
On Sun, Feb 19, 2017 at 9:01 AM, Tony Kurc
+1 (non-binding)
Verified signature, hashes
Contrib-check build against fresh local repo
Simple flow on 3 node cluster
On Sat, Feb 18, 2017 at 3:45 PM, Joe Witt wrote:
> James
>
> It is simply enough that someone volunteered to RM the release. If time is
> available to
Hey Rafael Carlos,
Unfortunately, remote process group output ports aren't currently supported
in MiNiFi [1]. There is currently a Jira case to support this
functionality [2].
Thanks,
Bryan
[1]
https://nifi.apache.org/minifi/system-admin-guide.html#remote-process-groups
[2]
Congrats!
On Tue, Feb 21, 2017 at 3:47 PM, Joe Percivall
wrote:
> Congrats Jeff!
>
> On Tue, Feb 21, 2017 at 3:33 PM, Yolanda Davis
> wrote:
>
> > Congratulations Jeff!
> >
> > On Tue, Feb 21, 2017 at 2:41 PM, Aldrin Piri
Congrats James!
On Wed, Feb 22, 2017 at 11:53 AM, Tony Kurc wrote:
> James,
> Glad to have you on the PMC! Congrats!
>
> On Wed, Feb 22, 2017 at 11:42 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
>
> > Congrats James! Well deserved!
> >
> > 2017-02-22 16:28
Verified GPG, checksums, built with:
https://github.com/brosander/dev-dockerfiles/tree/master/minifi/cpp/build/ubuntu
Ran example flow sending data to local nifi from Ubuntu-based docker
container with only libxml2-dev:
Congrats Matt!
Well deserved!
On Fri, Oct 7, 2016 at 11:54 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Matthew. . . congrats!
> Ohh wait, sorry I am actually referring to you Burgess, not that other one
> that is pounding your neighborhood at the moment.
> Anyway, stay
Congrats!
On Mon, Sep 19, 2016 at 3:51 PM, Andy LoPresto wrote:
> Congratulations Rob. Very exciting.
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
Hey Breandán,
session.create() will create a brand new FlowFile, not retrieve one from
the queue. I'd suggest session.get() if you're trying to retrieve incoming
FlowFiles.
Thanks,
Bryan
On Thu, Sep 22, 2016 at 11:52 AM, Breandan Mac Parland <
breandan.parl...@dbg.co.uk> wrote:
> Hi,
>
> I
Downloaded source
Verified checksums
Ran build with contrib-check and empty local repo
Ran build with –T2 concurrency and empty local repo
Used tls-toolkit to generate 4 localhost keystore, truststore,
nifi.properties and a single client certificate
Started all 4 instances verified no port
-probably-why-half-the-internet-shut-down-today-
> 1788062835
>
>
> Joe
>
> - - - - - -
> Joseph Percivall
> linkedin.com/in/Percivall
> e: joeperciv...@yahoo.com
>
>
>
> On Friday, October 21, 2016 10:04 AM, Bryan Rosander <
> bryanrosan...@gmail.com&
Trying to open that in a browser gives the same error and says no healthy
backends, maybe the npm registry is having issues?
Thanks,
Bryan
On Fri, Oct 21, 2016 at 10:02 AM, Joe Gresock wrote:
> Is anyone else getting a build failure on master?
>
> [WARNING] npm WARN
+1 (non-binding)
* Signature, hashes are good
* Full contrib-check build with empty .m2 works on macOS, Windows 10
* tls-toolkit secured 3-node cluster comes up fine, can set permissions,
create, start flow after changing relevant paths to 1.1.0 [1]
Can confirm readme issues seen by Jeff and Joe
he mistake he committed in Melbourne...
> :-)
>
> Cheers
>
> On Thu, Oct 27, 2016 at 4:15 AM, Joe Witt <joew...@apache.org> wrote:
>
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > Bryan Rosander has accepted the PMC's invitation to beco
Congrats Scott!
On Fri, Nov 4, 2016 at 11:50 AM, Rob Moran wrote:
> Congrats Scott - thanks for all the awesome work!
>
> Rob
>
> On Fri, Nov 4, 2016 at 11:43 AM, Pierre Villard <
> pierre.villard...@gmail.com
> > wrote:
>
> > Congrats! Well deserved is an euphemism ;-)
> >
>
Congrats Andre! Well deserved :)
On Fri, Nov 4, 2016 at 9:44 AM, Mark Payne wrote:
> Welcome, Andre!
>
> -Mark
>
> > On Nov 3, 2016, at 10:37 PM, Joe Witt wrote:
> >
> > Team,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that
Hi Gaurav,
You can expose ports in docker so they are reachable from the host machine
[1]. One trick I like to use is I have a container running an openssh
server that I SSH into and expose a local port [2]. Then I can point my
browser at localhost:1025 as a SOCKS proxy and tell it to do remote
Hi Pushkar,
In the tutorial you link to, it looks like before generating the template,
you need to select just subsection of the flow shown.
Currently MiNiFi does not support Input or Output ports in the root process
group so if you were to create a template from the whole flow, it would be
may arise at the conclusion of this voting
> >> process. I would also like to add dependency install commands as needed
> >> for the common platforms/package managers.
> >>
> >> On Wed, Nov 30, 2016 at 3:49 PM, Bryan Rosander <brosan...@apache.org>
> &g
+1 (non-binding)
Notes:
I needed to install uuid-dev to build on Ubuntu (not part of README.md).
I needed to install libleveldb-dev to build (part of README.md) as well as
to run (not part of README.md) on Ubuntu.
Validated signature, hashes, build, sample flow in Docker Ubuntu container.
On
+1 (non-binding)
Checked hashes, signature, full build with new mvn local repo and
contrib-check. Ran templates in
https://github.com/brosander/minifi-testkit/tree/master/templates which
includes one that sends data to NiFi and exercises the minifi-toolkit.
Everything seems to be working.
Notes:
Hi Tony,
S2S over HTTP was added to MiNiFi for 0.1.0 [1]. That work didn't include
the proxy properties though. I've written up a case to add this support
going forward [2].
Thanks,
Bryan
[1]: https://issues.apache.org/jira/browse/MINIFI-137
[2]:
Congrats Joe!
On Mon, Jan 2, 2017 at 7:53 PM, Andre wrote:
> Congratulations Joe!
>
> On Fri, Dec 30, 2016 at 5:02 AM, Aldrin Piri wrote:
>
> > All,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Joe
> Skora has
> > accepted the
+1 (non-binding)
- Ran through release helper
- Sent data to NiFi via S2S using MiNiFi without proxy, with proxy, with
authenticating proxy
On Sun, Dec 18, 2016 at 8:14 PM, Koji Kawamura
wrote:
> +1 (non-binding).
>
> - Ran through the release helper
> - Ran some basic
Congrats Jeremy!
On Tue, Dec 20, 2016 at 9:03 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Congrats Jeremy! Well deserved!
> > On Dec 20, 2016, at 8:46 AM, Yolanda Davis
> wrote:
> >
> > Congratulations Jeremy!
> >
> > On Mon, Dec 19, 2016 at 8:23 PM,
I'd think it should be a quick-start unsecured single instance by default
to lower barrier for people new to NiFi but I think we should support more
complex configurations with configuration from the user.
E.g. a lot of the database images will run any script
in /docker-entrypoint-initdb.d
+1
I would definitely like to help out with this effort.
On Wed, Dec 28, 2016 at 9:55 AM, Jeremy Dyer wrote:
> Team,
>
> I wanted to discuss getting an official Apache NiFi Docker image similar to
> other Apache projects like storm [1], httpd [2], thrift [3], etc.
>
>
+1 (non-binding)
Verified signature, checksums, contrib-check build with clean m2 repo.
Setup 3 node secured cluster with tls-toolkit
Tested s2s from MiNiFi with and without proxy.
On Thu, Dec 22, 2016 at 1:21 PM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:
> +1 (binding) Release
Hi Sunil,
Everything that the NiFi UI does is performed via a REST API [1]. You
could write your own front end that utilizes that API to perform operations.
There are also processors that contribute their own UI [2] so you could
potentially go down that road if you wanted.
Thanks,
Bryan
[1]
Congrats Bin!
On Wed, Apr 5, 2017 at 9:52 AM, Oleg Zhurakousky wrote:
> And of course I did it in the wrong thread ;)
> Congrats Bin!!!
>
> > On Apr 5, 2017, at 9:48 AM, Oleg Zhurakousky wrote:
> >
> > Thank you all!
> >
> > >> *Joe Percivall*
> >> e:
Congrats Oleg!
On Wed, Apr 5, 2017 at 9:53 AM, Oleg Zhurakousky
wrote:
> Thank you all!
>
> > *Joe Percivall*
> > e: joeperciv...@gmail.com
>
>
Hi Mark,
To my knowledge there's no reason it shouldn't work in Chrome. Have you
tried the "Empty Cache and Hard Reload" option to verify you don't have
outdated javascript, etc files cached?
Thanks,
Bryan
On Fri, Apr 21, 2017 at 11:25 AM, Mark Bean wrote:
> I built
I'm definitely in favor of smaller images, especially given the nature of
the subproject. I think the MiNiFi Java image may be able to benefit from
Alpine as well.
Thanks,
Bryan
On Wed, Apr 26, 2017 at 11:09 AM, Aldrin Piri wrote:
> Don't think there would be any
+1 non-binding
Verified signature, checkums
Ran build with docker and contrib-check (mvn -P docker -P contrib-check
clean install) and empty m2 folder
Set up c2 docker-compose configuration with a delegating c2 server,
authoritative c2 server pointing at nifi cluster, 5 minifi nodes
Tested a
+1
It looks like winsw would be a good option. I noticed it also supports
arbitrary executables, not just Java programs. That would mean we could
use it for both C++ and Java implementations unless there's a good reason
not to (once C++ version can run on Windows).
On Mon, Jun 26, 2017 at 2:45
Hey Mark,
The Site-to-Site client attempts to load balance based on the number of
flow files each node is currently processing combined with some randomness.
[1]
Thanks,
Bryan
[1]
Congrats Yolanda!
On Thu, May 18, 2017 at 9:04 AM, Kevin Doran
wrote:
> Congratulations, Yolanda! As everyone has said, very well deserved! Thanks
> for all you do for the NiFi project and community.
>
> Kevin
>
> On 5/17/17, 22:11, "Tony Kurc" wrote:
Congrats Pierre!
On Tue, May 23, 2017 at 11:19 AM, Pierre Villard <
pierre.villard...@gmail.com> wrote:
> Thanks all! Very much appreciated!! Looking forward the amazing stuff to
> come!
>
> 2017-05-23 1:30 GMT+02:00 Andre :
>
> > Pierre,
> >
> > Your contribution to NiFi
Hi Xophos,
You need to ensure that all the ports are different if you're running the
instances on a single machine. That includes the http(s) port.
Your operating system will not let multiple processes bind to the same ip
address and port.
Relevant portion of the exception:
Congrats Koji!
On Tue, May 30, 2017 at 10:38 AM, Scott Aslan wrote:
> Congrats Koji!
>
> On Tue, May 30, 2017 at 8:44 AM, Jeff wrote:
>
> > Contrats, Koji!
> >
> > On Sun, May 28, 2017 at 12:33 PM Matt Burgess
> > wrote:
> >
> >
+1 (non-binding)
Verified signature, hashes
contrib-check build with fresh m2 folder
simple flow testing s2s from MiNiFi Java and C++ to secured and unsecured
nifi clusters
On Wed, Jun 7, 2017 at 12:48 PM, Kevin Doran
wrote:
> +1 (non-binding), release this package as
Congrats Drew!
On Wed, May 31, 2017 at 3:51 PM, Andrew Psaltis
wrote:
> Congrats Drew! I spend a lot of time teaching people about NiFi and can
> honestly say the documentation -- built-in and on the wiki is a great
> selling point. Thanks for all the hard work.
>
> On
Congrats Marc! Thanks for all the C++ help so far :)
On Thu, Jun 1, 2017 at 8:48 AM, Scott Aslan wrote:
> Congrats Marc!
>
> On Thu, Jun 1, 2017 at 8:39 AM, Marc wrote:
>
> > Thank you, everyone! Amazing to be part of such a cohesive and
>
Hey Pierre,
You can version the metadata db in the root dir of the git repo with event
hooks.
With an h2 jdbc url of
'jdbc:h2:$NIFI_REGISTRY_HOME/database/nifi-registry-primary;AUTOCOMMIT=OFF;LOCK_MODE=3;LOCK_TIMEOUT=25000;WRITE_DELAY=0;AUTO_SERVER=TRUE'
You can connect to the db in a separate
uld be completely behind the scenes or not, but if
> it was going to be a first class concept then we'd need to put some
> design and thought into how it fits into the UX.
>
> Thanks,
>
> Bryan
>
> [1]
> https://github.com/apache/nifi-registry/blob/master/nifi-registry-
Hi all,
We're trying to implement a feature branch workflow with NiFi Registry.
The basic idea is that you'd be able to have one or more branches off of
master and then the capability to merge changes back in when they're ready.
Our flow has many versioned process groups that are nested several
y we can still freely modify it as needed, but
> can just switch the impl through something in
> nifi-registry.properties.
>
>
>
> On Tue, Mar 5, 2019 at 1:29 PM Bryan Rosander
> wrote:
> >
> > Thanks for the quick response!
> >
> > As far as the
I've seen similar issues building locally on OSx. I tried going back and
building 1.8.0 and saw similar behavior as master.
Haven't been able to sort it out yet though.
Thanks,
Bryan
On Thu, Mar 14, 2019 at 6:41 PM Ryan Withers wrote:
> Hello all,
>
> I'm encountering an error in the
59 matches
Mail list logo