Re: [ANNOUNCE] Apache NiFi 1.1.0 Release

[Andy LoPresto]

Can we update this template to use the HTTPS links for the main site and 
download pages? Thanks. 

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Nov 30, 2016, at 13:31, Joe Witt  wrote:
> 
> Hello
> 
> The Apache NiFi team would like to announce the release of Apache NiFi 1.1.0.
> 
> Apache NiFi is an easy to use, powerful, and reliable system to
> process and distribute data.  Apache NiFi was made for dataflow.  It
> supports highly configurable directed graphs of data routing,
> transformation, and system mediation logic.
> 
> This release is the result of fantastic community contribution across
> feature requests, documentation, bug reports, code contributions,
> reviews, and release validation.
> 
> The release highlights:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.1.0
> 
> More details on Apache NiFi can be found here:
>  http://nifi.apache.org/
> 
> The release artifacts can be downloaded from here:
>  http://nifi.apache.org/download.html
> 
> Maven artifacts have been made available here:
>  https://repository.apache.org/content/repositories/releases/org/apache/nifi/
> 
> Issues closed/resolved for this list can be found here:
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12337875
> 
> Thank you
> The Apache NiFi team

Re: [VOTE] Release Apache NiFi - MiNiFi 0.1.0 (RC1)

[Bryan Bende]

+1 (binding) Release this package as minifi-0.1.0

- Ran through helper with no issues
- Tested sample flow with MiNiFi on Raspberry Pi to NiFi on laptop and
working as expected

On Thu, Dec 1, 2016 at 2:55 PM, Andy LoPresto  wrote:

> +1 (binding)
>
> Checked the hashes and GPG signature, verified contrib-check and all tests
> pass and the build works on OS X 10.11.6, and ran a simple TailFile flow
> reporting back to NiFi.
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Dec 1, 2016, at 11:35 AM, Bryan Rosander  wrote:
>
> +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:
> When testing
> https://github.com/brosander/minifi-testkit/blob/master/templates/
> InvokeHttpMiNiFiTemplateTest.xml
> I saw xml validation errors that don't seem to impact functionality.  As
> they are caused by NiFi libraries, I captured findings in
> https://issues.apache.org/jira/browse/NIFI-3138
>
> On Thu, Dec 1, 2016 at 12:16 PM, Joe Percivall <
> joeperciv...@yahoo.com.invalid> wrote:
>
> +1 Release this package as minifi-0.1.0
> Ran through the helper. Built and tested on OSX 10.10.5, Windows 8.1 and
> RHEL 7.2. Everything worked as expected.
>
> Thanks for acting as RM Aldrin,Joe
> - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
> joeperciv...@yahoo.com
>
>
> On Thursday, December 1, 2016, 12:09:38 AM EST, Aldrin Piri <
> ald...@apache.org> wrote:Hello
> I am pleased to be calling this vote for the source release of Apache NiFi
> - MiNiFi, minifi-0.1.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi/0.1.0/
> The Git tag is minifi-0.1.0-RC1
> The Git commit ID is 6e7f05d4bef3637a829c17435eb9eff83aa6b810*
> https://git-wip-us.apache.org/ repos/asf?p=nifi-minifi.git;a=commit;h=
> 6e7f05d4bef3637a829c17435eb9eff83aa6b810* https://github.
> com/apache/nifi-minifi/commit/6e7f05d4bef3637a829c17435eb9eff83aa6b810
> Checksums of nifi-0.0.1-source-release.zip:
> MD5: 9d44398bc1eec7d5596ad425bbb9257b
> SHA1: d8043759eb53d815badccf9136a239103aa914dfSHA256:
> c740a2765c74b6bda7ab0ef3ee57353e8c26cb5009f8949a3349af7ded0be181
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/aldrin.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 29 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12335482
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/MINIFI/
> Release+Notes#ReleaseNotes-Version0.1.0
>
> The vote will be open for 72 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as minifi-0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
>
>

Another holiday request...

[Russell Bateman]

In pursuit of yet more wacky functionality, I wondered about a good way 
to get a NiFi user's attention (yeah, the person standing looking at the 
UI) when some condition, threshold, etc. is met as detected by a custom 
processor. In view of the season, is it possible to turn the processor 
representation flashing green or red?


Okay, seriously, I guess I could just throw ProcessExceptionor 
discretely (sniff) drop something into the log. (Do any better ideas 
comes to mind?)


If NiFi is to gain greater public recognition and popularity, we need to 
consider how to attract Hollywood through cool visual effects. I'm 
anticipating seeing Tom Cruise looking at NiFi on-screen during a tense 
moment in MI-6!


;-)

Thanks,

Russ

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Joe Percivall]

+1 (binding) Release this package as nifi-minifi-cpp-0.1.0

Ran through the helper. Built and tested on OSX 10.10.5 and RHEL 7.2. 
Did run into a bit of a hiccup when RHEL 7.2 when using the GetFile processor a 
relative path wasn't working for the input directory and when I didn't specify 
the "FileFilter" it said "[2016-12-01 17:04:43.461] [minifi log] [error] 
Invalid File Filter regex: regex_error." 
Aside from those two, things worked as expected.

Joe
- - - - - - 
Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com


On Thursday, December 1, 2016, 2:51:05 PM EST, Andy LoPresto 
 wrote:+1 (binding)
I downloaded the assets, verified all checksums and GPG signature, and built 
the app. Initially encountered a problem on OS X 10.11.6 because I used 
ossp-uuid library, but with Aldrin’s help was able to remove that and use 
libuuid. Ran a simple GetFile demo and sent data back to a NiFi instance. 

Andy LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP Fingerprint: 
70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Dec 1, 2016, at 8:18 AM, Ben Qiu  wrote:
+1


On 2016-11-29 08:54 (-0800), Aldrin Piri  wrote:


Hello Apache NiFi Community,>







I am pleased to be calling this vote for the source release of Apache

NiFi MiNiFi C++, nifi-minifi-cpp-0.1.0.>






The source archive, signature, and digests can be located at:>







Source Archive:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz







GPG armored signature:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc







Source MD5:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5







Source SHA1:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1







Source SHA256:>





https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256











The Git tag is minifi-cpp-0.1.0-RC1>



The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186>



*

https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
<
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186







*

https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
<
https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186











Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:>



MD5: a7155f53d86ef93e37bf28d6e4a0299f>



SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd>



SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d47b66>











Release artifacts are signed with the following key:>



https://people.apache.org/keys/committer/aldrin <

https://people.apache.org/keys/committer/aldrin>>






KEYS file available here:>



https://dist.apache.org/repos/dist/release/nifi/KEYS <

https://dist.apache.org/repos/dist/release/nifi/KEYS>>






15 issues were closed/resolved for this release:>





https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
<
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921











Release note highlights can be found here:>





https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
<
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0











The vote will be open for 72 hours.>



Please download the release candidate and evaluate the necessary items>



including checking hashes, signatures, build from source, and test. Then>



please vote:>







[ ] +1 Release this package as nifi-minifi-cpp-0.1.0>



[ ] +0 no opinion>



[ ] -1 Do not release this package because...>

Re: How to log what flowfile is getting passed out from each Processor

[srini]

Thanks a lot Bryan.



--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/How-to-log-what-flowfile-is-getting-passed-out-from-each-Processor-tp14088p14111.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Native "Remote Process Groups" service - as an Integration approach

[Stefán Baxter]

Hi,

This may be a silly question, please forgive me.

We are trying integrating our platform with Nifi in an as efficient way as
possible and we have been implementing the same "port based" integrations
as used for stream processing solutions.

The nifi-site-to-site-client library makes this very easy but the IN or OUT
port approach seems slightly "disjoint", at least in comparison with remote
process groups which support both IN and OUT

And here is the question. Is there a library available which would allow a
solution to provide a Nifi compatable "Remote Process Group" service
without being a complete Nifi server?

All the best,
 -Stefán

Re: New UI Overview video

[Matt Gilman]

Thanks Jenn!

The new video is awesome. I just published it to the site. It is live now.

Matt

On Thu, Dec 1, 2016 at 1:16 PM, Andy LoPresto  wrote:

> Jenn,
>
> This is great stuff. Thanks for creating these. We will get them on the
> site quickly.
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Dec 1, 2016, at 3:32 AM, Jennifer Barnabee 
> wrote:
>
> Hello Apache NiFi team -
> I created the following update to the toolbar overview video to show off
> the new UI:
>
> https://youtu.be/Y5znvcJ_NWo
>
> If you like it, feel free to use it to replace the one entitled
> "Screencast: NiFi Toolbar Overview" on the Apache NiFi web site. (It has
> the creative commons license.) I suggest calling this one, "Screencast:
> NiFi User Interface Overview".
>
> I hope to update the other videos using the new UI as well.
>
> Cheers,
> Jenn
>
> P.S. Here is the embed code:
>
> https://www.youtube.com/embed/Y5znvcJ_NWo; frameborder="0"
> allowfullscreen>
>
>
>

Re: Error creating Transactions for SiteToSite connections

[Stefán Baxter]

Hi Brian,

Thank you for pointing to these. I'm going to try to figure this out, based
on these, but I will send a link to my code if that does not pan out :).

Thnx,
 -Stefán

On Thu, Dec 1, 2016 at 6:07 PM, Bryan Bende  wrote:

> Hi Stefan,
>
> Glad to hear NiFi is helping your team!
>
> It sounds like you probably already have the code part down, but what does
> your code for sending or receiving look code?
>
> There are some examples here...
>
> Sending -
> https://github.com/apache/nifi/blob/master/nifi-
> external/nifi-storm-spout/src/main/java/org/apache/nifi/
> storm/NiFiBolt.java#L144-L156
> Receiving -
> https://github.com/apache/nifi/blob/master/nifi-
> external/nifi-storm-spout/src/main/java/org/apache/nifi/
> storm/NiFiSpout.java#L202
>
> Is it possible there are network issues between whatever system and your
> NiFi system? have you tried from different systems to see if it is always a
> problem or maybe there is only a couple of servers that have trouble
> talking to NiFi?
>
> Thanks,
>
> Bryan
>
>
> On Thu, Dec 1, 2016 at 12:42 PM, Stefán Baxter 
> wrote:
>
> > Hi.
> >
> > I'm new here and would like to start by thanking for Nifi which is
> helping
> > us here at Activity Stream a lot.
> >
> > I have a question regarding a "SiteToSite connector" we are developing to
> > make some of our services play-nice with Nifi and I'm not sure if you
> want
> > those to the dev or the user channel (as I'm not contributing (yet) to
> > Nifi) :).
> >
> > We have established a connection and successfully communicated with both
> > IN/OUT ports.
> >
> > Sometimes the communication channels seems to get stuck and we can not
> > create any new transactions:
> >
> >- IOException: "Unable to create Transaction to communicate with
> >Peer[url=nifi://tornado:1234,CLOSED]"
> >- Nifi console: complains about a request timing out (I assume on the
> on
> >the return/heartbeat path)
> >- Sometimes this starts working again after a long-while but only for
> >1-2 successful deliveries
> >
> > We have tried everything that has come to mind to "reboot" this,
> including
> > creating a new SiteToSiteClient connection to use, but to no avail.
> >
> > Am I falling into a known newbe hole or can anyone point me to some
> > material that would help me do this properly?
> >
> > Best regards,
> >  -Stefán
> >
>

Re: How to log what flowfile is getting passed out from each Processor

[srini]

Thanks Bryan.

In the lineage graph, I see a flow chart. I don't see any content of each
event etc., as you described. 

thanks
Srini



--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/How-to-log-what-flowfile-is-getting-passed-out-from-each-Processor-tp14088p14103.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: [VOTE] Release Apache NiFi - MiNiFi 0.1.0 (RC1)

[Andy LoPresto]

+1 (binding)

Checked the hashes and GPG signature, verified contrib-check and all tests pass 
and the build works on OS X 10.11.6, and ran a simple TailFile flow reporting 
back to NiFi.

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Dec 1, 2016, at 11:35 AM, Bryan Rosander  wrote:
> 
> +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:
> When testing
> https://github.com/brosander/minifi-testkit/blob/master/templates/InvokeHttpMiNiFiTemplateTest.xml
> I saw xml validation errors that don't seem to impact functionality.  As
> they are caused by NiFi libraries, I captured findings in
> https://issues.apache.org/jira/browse/NIFI-3138
> 
> On Thu, Dec 1, 2016 at 12:16 PM, Joe Percivall <
> joeperciv...@yahoo.com.invalid> wrote:
> 
>> +1 Release this package as minifi-0.1.0
>> Ran through the helper. Built and tested on OSX 10.10.5, Windows 8.1 and
>> RHEL 7.2. Everything worked as expected.
>> 
>> Thanks for acting as RM Aldrin,Joe
>> - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
>> joeperciv...@yahoo.com
>> 
>> 
>> On Thursday, December 1, 2016, 12:09:38 AM EST, Aldrin Piri <
>> ald...@apache.org> wrote:Hello
>> I am pleased to be calling this vote for the source release of Apache NiFi
>> - MiNiFi, minifi-0.1.0.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi/0.1.0/
>> The Git tag is minifi-0.1.0-RC1
>> The Git commit ID is 6e7f05d4bef3637a829c17435eb9eff83aa6b810*
>> https://git-wip-us.apache.org/ repos/asf?p=nifi-minifi.git;a=commit;h=
>> 6e7f05d4bef3637a829c17435eb9eff83aa6b810* https://github.
>> com/apache/nifi-minifi/commit/6e7f05d4bef3637a829c17435eb9eff83aa6b810
>> Checksums of nifi-0.0.1-source-release.zip:
>> MD5: 9d44398bc1eec7d5596ad425bbb9257b
>> SHA1: d8043759eb53d815badccf9136a239103aa914dfSHA256:
>> c740a2765c74b6bda7ab0ef3ee57353e8c26cb5009f8949a3349af7ded0be181
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/aldrin.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 29 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12316020=12335482
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/MINIFI/
>> Release+Notes#ReleaseNotes-Version0.1.0
>> 
>> The vote will be open for 72 hours.
>> 
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test.
>> Then please vote:
>> 
>> [ ] +1 Release this package as minifi-0.1.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Andy LoPresto]

+1 (binding)

I downloaded the assets, verified all checksums and GPG signature, and built 
the app. Initially encountered a problem on OS X 10.11.6 because I used 
ossp-uuid library, but with Aldrin’s help was able to remove that and use 
libuuid. Ran a simple GetFile demo and sent data back to a NiFi instance.


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Dec 1, 2016, at 8:18 AM, Ben Qiu  wrote:
> 
> +1
> 
> 
> On 2016-11-29 08:54 (-0800), Aldrin Piri  wrote:
> 
>> Hello Apache NiFi Community,>
> 
>> 
> 
>> I am pleased to be calling this vote for the source release of Apache
> NiFi MiNiFi C++, nifi-minifi-cpp-0.1.0.>
> 
>> 
> 
>> The source archive, signature, and digests can be located at:>
> 
>> 
> 
>> Source Archive:>
> 
>> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
>>> 
> 
>> GPG armored signature:>
> 
>> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
>>> 
> 
>> Source MD5:>
> 
>> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
>>> 
> 
>> Source SHA1:>
> 
>> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
>>> 
> 
>> Source SHA256:>
> 
>> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
>>> 
> 
>> 
> 
>> The Git tag is minifi-cpp-0.1.0-RC1>
> 
>> The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186>
> 
>> *
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
> <
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
>>> 
> 
>> *
> https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
> <
> https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
>>> 
> 
>> 
> 
>> Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:>
> 
>> MD5: a7155f53d86ef93e37bf28d6e4a0299f>
> 
>> SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd>
> 
>> SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d47b66>
> 
>> 
> 
>> 
> 
>> Release artifacts are signed with the following key:>
> 
>> https://people.apache.org/keys/committer/aldrin <
> https://people.apache.org/keys/committer/aldrin>>
> 
>> 
> 
>> KEYS file available here:>
> 
>> https://dist.apache.org/repos/dist/release/nifi/KEYS <
> https://dist.apache.org/repos/dist/release/nifi/KEYS>>
> 
>> 
> 
>> 15 issues were closed/resolved for this release:>
> 
>> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
>>> 
> 
>> 
> 
>> Release note highlights can be found here:>
> 
>> 
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
> <
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
>>> 
> 
>> 
> 
>> The vote will be open for 72 hours.>
> 
>> Please download the release candidate and evaluate the necessary items>
> 
>> including checking hashes, signatures, build from source, and test. Then>
> 
>> please vote:>
> 
>> 
> 
>> [ ] +1 Release this package as nifi-minifi-cpp-0.1.0>
> 
>> [ ] +0 no opinion>
> 
>> [ ] -1 Do not release this package because...>
> 
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Bryan Bende]

+1 (binding) Release this package as nifi-minifi-cpp-0.1.0

A couple of notes...

- I had some initial troubles building and running on my laptop (OSX
10.10.5), but after installing lib uuid from source rather than brew
ossp-uuid, I was able to run on my laptop sending data to a regular NiFi
instance.

- I noticed when extracting the source that there was a .git directory in
it. Not that this really seems like a problem, but should that actually be
under version control?

- In addition to my laptop, I compiled and ran on a Raspberry Pi 2 Model B
running Raspbian Jesse, and I had the Pi connected to my laptop over
ethernet... It would connect to NiFi on my laptop and send some data
successfully, but then sometimes I would see this:

[2016-11-30 22:32:38.635] [minifi log] [info] Site2Site Send FINISH
TRANSACTION for transaction 71e57d6e-c251-4f35-ad99-3023ddf9771a
[2016-11-30 22:32:38.639] [minifi log] [info] Site2Site transaction
71e57d6e-c251-4f35-ad99-3023ddf9771a peer confirm transaction with CRC
3404584822
[2016-11-30 22:32:38.639] [minifi log] [info] Site2Site transaction
71e57d6e-c251-4f35-ad99-3023ddf9771a CRC not matched -890382474
[2016-11-30 22:32:38.639] [minifi log] [info] Site2Site delete transaction
71e57d6e-c251-4f35-ad99-3023ddf9771a

Then at the same time in the NiFi logs I would see this:

2016-11-30 17:38:50,162 INFO [Site-to-Site Worker Thread-67]
o.a.nifi.remote.SocketRemoteSiteListener Successfully negotiated
ServerProtocol SocketFlowFileProtocol Version 5 with
Peer[url=nifi://raspberrypi.local:35510]2016-11-30 17:38:50,289 ERROR
[Site-to-Site Worker Thread-67] o.a.nifi.remote.SocketRemoteSiteListener
Unable to communicate with remote instance
Peer[url=nifi://raspberrypi.local:35510]
(SocketFlowFileServerProtocol[CommsID=77842d17-b31d-4601-9f0d-38fd0b2fc7cc])
due to org.apache.nifi.processor.exception.ProcessException:
java.io.IOException:
SocketFlowFileServerProtocol[CommsID=77842d17-b31d-4601-9f0d-38fd0b2fc7cc]
Received a BadChecksum response from peer
Peer[url=nifi://raspberrypi.local:35510]; closing connection

Once it got into this state I would have to restart the process, and
sometimes this would even happen on the first file I tried to send through.

It is most likely something in my environment since everything worked fine
when it was local on my laptop, and I believe Koji and maybe a few others
ran on a Raspberry Pi as well, but I thought I would mention it in case it
turns out to be an actual issue.

On Thu, Dec 1, 2016 at 11:18 AM, Ben Qiu  wrote:

> +1
>
>
> On 2016-11-29 08:54 (-0800), Aldrin Piri  wrote:
>
> > Hello Apache NiFi Community,>
>
> >
>
> > I am pleased to be calling this vote for the source release of Apache
> NiFi MiNiFi C++, nifi-minifi-cpp-0.1.0.>
>
> >
>
> > The source archive, signature, and digests can be located at:>
>
> >
>
> > Source Archive:>
>
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
> >>
>
> > GPG armored signature:>
>
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
> >>
>
> > Source MD5:>
>
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
> >>
>
> > Source SHA1:>
>
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
> >>
>
> > Source SHA256:>
>
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
> <
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
> >>
>
> >
>
> > The Git tag is minifi-cpp-0.1.0-RC1>
>
> > The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186>
>
> > *
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=
> bd963503586aeb9b24b4ad5a96da9a1a6818a186
> <
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=
> bd963503586aeb9b24b4ad5a96da9a1a6818a186
> >>
>
> > *
> https://github.com/apache/nifi-minifi-cpp/commit/
> bd963503586aeb9b24b4ad5a96da9a1a6818a186
> <
> https://github.com/apache/nifi-minifi-cpp/commit/
> bd963503586aeb9b24b4ad5a96da9a1a6818a186
> >>
>
> >
>
> > Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:>
>
> > MD5: a7155f53d86ef93e37bf28d6e4a0299f>
>
> > SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd>
>
> > SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d4
> 7b66>
>
> >

Re: [VOTE] Release Apache NiFi - MiNiFi 0.1.0 (RC1)

[Bryan Rosander]

+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:
When testing
https://github.com/brosander/minifi-testkit/blob/master/templates/InvokeHttpMiNiFiTemplateTest.xml
I saw xml validation errors that don't seem to impact functionality.  As
they are caused by NiFi libraries, I captured findings in
https://issues.apache.org/jira/browse/NIFI-3138

On Thu, Dec 1, 2016 at 12:16 PM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:

> +1 Release this package as minifi-0.1.0
> Ran through the helper. Built and tested on OSX 10.10.5, Windows 8.1 and
> RHEL 7.2. Everything worked as expected.
>
> Thanks for acting as RM Aldrin,Joe
> - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
> joeperciv...@yahoo.com
>
>
> On Thursday, December 1, 2016, 12:09:38 AM EST, Aldrin Piri <
> ald...@apache.org> wrote:Hello
> I am pleased to be calling this vote for the source release of Apache NiFi
> - MiNiFi, minifi-0.1.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi/0.1.0/
> The Git tag is minifi-0.1.0-RC1
> The Git commit ID is 6e7f05d4bef3637a829c17435eb9eff83aa6b810*
> https://git-wip-us.apache.org/ repos/asf?p=nifi-minifi.git;a=commit;h=
> 6e7f05d4bef3637a829c17435eb9eff83aa6b810* https://github.
> com/apache/nifi-minifi/commit/6e7f05d4bef3637a829c17435eb9eff83aa6b810
> Checksums of nifi-0.0.1-source-release.zip:
> MD5: 9d44398bc1eec7d5596ad425bbb9257b
> SHA1: d8043759eb53d815badccf9136a239103aa914dfSHA256:
> c740a2765c74b6bda7ab0ef3ee57353e8c26cb5009f8949a3349af7ded0be181
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/aldrin.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 29 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12335482
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/MINIFI/
> Release+Notes#ReleaseNotes-Version0.1.0
>
> The vote will be open for 72 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as minifi-0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

Re: New UI Overview video

[Andy LoPresto]

Jenn,

This is great stuff. Thanks for creating these. We will get them on the site 
quickly.

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Dec 1, 2016, at 3:32 AM, Jennifer Barnabee  
> wrote:
> 
> Hello Apache NiFi team -
> I created the following update to the toolbar overview video to show off
> the new UI:
> 
> https://youtu.be/Y5znvcJ_NWo
> 
> If you like it, feel free to use it to replace the one entitled
> "Screencast: NiFi Toolbar Overview" on the Apache NiFi web site. (It has
> the creative commons license.) I suggest calling this one, "Screencast:
> NiFi User Interface Overview".
> 
> I hope to update the other videos using the new UI as well.
> 
> Cheers,
> Jenn
> 
> P.S. Here is the embed code:
> 
> https://www.youtube.com/embed/Y5znvcJ_NWo; frameborder="0"
> allowfullscreen>



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Error creating Transactions for SiteToSite connections

[Bryan Bende]

Hi Stefan,

Glad to hear NiFi is helping your team!

It sounds like you probably already have the code part down, but what does
your code for sending or receiving look code?

There are some examples here...

Sending -
https://github.com/apache/nifi/blob/master/nifi-external/nifi-storm-spout/src/main/java/org/apache/nifi/storm/NiFiBolt.java#L144-L156
Receiving -
https://github.com/apache/nifi/blob/master/nifi-external/nifi-storm-spout/src/main/java/org/apache/nifi/storm/NiFiSpout.java#L202

Is it possible there are network issues between whatever system and your
NiFi system? have you tried from different systems to see if it is always a
problem or maybe there is only a couple of servers that have trouble
talking to NiFi?

Thanks,

Bryan


On Thu, Dec 1, 2016 at 12:42 PM, Stefán Baxter 
wrote:

> Hi.
>
> I'm new here and would like to start by thanking for Nifi which is helping
> us here at Activity Stream a lot.
>
> I have a question regarding a "SiteToSite connector" we are developing to
> make some of our services play-nice with Nifi and I'm not sure if you want
> those to the dev or the user channel (as I'm not contributing (yet) to
> Nifi) :).
>
> We have established a connection and successfully communicated with both
> IN/OUT ports.
>
> Sometimes the communication channels seems to get stuck and we can not
> create any new transactions:
>
>- IOException: "Unable to create Transaction to communicate with
>Peer[url=nifi://tornado:1234,CLOSED]"
>- Nifi console: complains about a request timing out (I assume on the on
>the return/heartbeat path)
>- Sometimes this starts working again after a long-while but only for
>1-2 successful deliveries
>
> We have tried everything that has come to mind to "reboot" this, including
> creating a new SiteToSiteClient connection to use, but to no avail.
>
> Am I falling into a known newbe hole or can anyone point me to some
> material that would help me do this properly?
>
> Best regards,
>  -Stefán
>

Error creating Transactions for SiteToSite connections

[Stefán Baxter]

Hi.

I'm new here and would like to start by thanking for Nifi which is helping
us here at Activity Stream a lot.

I have a question regarding a "SiteToSite connector" we are developing to
make some of our services play-nice with Nifi and I'm not sure if you want
those to the dev or the user channel (as I'm not contributing (yet) to
Nifi) :).

We have established a connection and successfully communicated with both
IN/OUT ports.

Sometimes the communication channels seems to get stuck and we can not
create any new transactions:

   - IOException: "Unable to create Transaction to communicate with
   Peer[url=nifi://tornado:1234,CLOSED]"
   - Nifi console: complains about a request timing out (I assume on the on
   the return/heartbeat path)
   - Sometimes this starts working again after a long-while but only for
   1-2 successful deliveries

We have tried everything that has come to mind to "reboot" this, including
creating a new SiteToSiteClient connection to use, but to no avail.

Am I falling into a known newbe hole or can anyone point me to some
material that would help me do this properly?

Best regards,
 -Stefán

Re: Nifi Group Processors Monitoring

[Jeff]

Hello Manee,

Processors support scheduling via a Timer Driven or CRON Driven scheduling
strategy.  Timer Driver is based on a time period, such as every 5 seconds,
or every 12 hours, etc.  CRON Driven uses the CRON format.  You can also
use the REST API to start and stop processors remotely.

In terms of monitoring, some statistics like bytes in/out, flowfiles
in/out, tasks and execution time for the last 5 minutes are shown directly
on the processor view in the UI.  You can right-click on a processor to
view more in-depth status by clicking on Status History, which will allow
you to view more statistics like the ones previously listed with more
control over the time period you'd like to view those statstics.  You can
also access Data Provenance for a processor by right-clicking on it and
selecting the Data Provenance option.  You'll be able to see all the
flowfiles that have been processed by that processor.  The duration for
which Data Provenance is available for a flowfile is configurable, by
default I think it's 24 hours/1GB of data.

For notifications, bulletins are shown in the top-right corner of a
processor, typically for processor configuration validation errors, and
warnings or errors during the processing of flowfiles.

Is this the kind of information are you looking for, or do you need
something more in-depth?

On Thu, Dec 1, 2016 at 7:36 AM Manee  wrote:

> Hi Team,
>
> I am working on Nifi Monitoring and Scheduling .In that I am trying to
> Find the solution on NiFi Scheduling. How to run processor in single window
> and monitoring it and Error should be highlighted as notification.I am
> stuck
> up on to find a solution. please help me out to find a solution
>
>
>
> Thanks,
> Manee
>
>
>
>
> -
> Thanks,
> Manee
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Group-Processors-Monitoring-tp14083.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>

Re: [VOTE] Release Apache NiFi - MiNiFi 0.1.0 (RC1)

[Joe Percivall]

+1 Release this package as minifi-0.1.0
Ran through the helper. Built and tested on OSX 10.10.5, Windows 8.1 and RHEL 
7.2. Everything worked as expected.

Thanks for acting as RM Aldrin,Joe
- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com


On Thursday, December 1, 2016, 12:09:38 AM EST, Aldrin Piri  
wrote:Hello
I am pleased to be calling this vote for the source release of Apache NiFi - 
MiNiFi, minifi-0.1.0.

The source zip, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi/0.1.0/
The Git tag is minifi-0.1.0-RC1
The Git commit ID is 6e7f05d4bef3637a829c17435eb9eff83aa6b810* 
https://git-wip-us.apache.org/ 
repos/asf?p=nifi-minifi.git;a=commit;h=6e7f05d4bef3637a829c17435eb9eff83aa6b810*
 
https://github.com/apache/nifi-minifi/commit/6e7f05d4bef3637a829c17435eb9eff83aa6b810
Checksums of nifi-0.0.1-source-release.zip:
MD5: 9d44398bc1eec7d5596ad425bbb9257b
SHA1: d8043759eb53d815badccf9136a239103aa914dfSHA256: 
c740a2765c74b6bda7ab0ef3ee57353e8c26cb5009f8949a3349af7ded0be181

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/aldrin.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

29 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12335482

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Version0.1.0

The vote will be open for 72 hours. 

Please download the release candidate and evaluate the necessary items 
including checking hashes, signatures, build from source, and test.
Then please vote:

[ ] +1 Release this package as minifi-0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Ben Qiu]

+1


On 2016-11-29 08:54 (-0800), Aldrin Piri  wrote:

> Hello Apache NiFi Community,>

>

> I am pleased to be calling this vote for the source release of Apache
NiFi MiNiFi C++, nifi-minifi-cpp-0.1.0.>

>

> The source archive, signature, and digests can be located at:>

>

> Source Archive:>

>
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
>>

> GPG armored signature:>

>
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
>>

> Source MD5:>

>
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
>>

> Source SHA1:>

>
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
>>

> Source SHA256:>

>
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
<
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
>>

>

> The Git tag is minifi-cpp-0.1.0-RC1>

> The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186>

> *
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
<
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
>>

> *
https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
<
https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
>>

>

> Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:>

> MD5: a7155f53d86ef93e37bf28d6e4a0299f>

> SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd>

> SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d47b66>

>

>

> Release artifacts are signed with the following key:>

> https://people.apache.org/keys/committer/aldrin <
https://people.apache.org/keys/committer/aldrin>>

>

> KEYS file available here:>

> https://dist.apache.org/repos/dist/release/nifi/KEYS <
https://dist.apache.org/repos/dist/release/nifi/KEYS>>

>

> 15 issues were closed/resolved for this release:>

>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
<
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
>>

>

> Release note highlights can be found here:>

>
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
<
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
>>

>

> The vote will be open for 72 hours.>

> Please download the release candidate and evaluate the necessary items>

> including checking hashes, signatures, build from source, and test. Then>

> please vote:>

>

> [ ] +1 Release this package as nifi-minifi-cpp-0.1.0>

> [ ] +0 no opinion>

> [ ] -1 Do not release this package because...>

>

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Binqiang Qiu]

+1

On 2016-11-29 08:54 (-0800), Aldrin Piri  wrote: 
> Hello Apache NiFi Community,> 
> 
> I am pleased to be calling this vote for the source release of Apache NiFi 
> MiNiFi C++, nifi-minifi-cpp-0.1.0.> 
> 
> The source archive, signature, and digests can be located at:> 
> 
> Source Archive:> 
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
>  
> >
>  
> GPG armored signature:> 
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
>  
> >
>  
> Source MD5:> 
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
>  
> >
>  
> Source SHA1:> 
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
>  
> >
>  
> Source SHA256:> 
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
>  
> >
>  
> 
> The Git tag is minifi-cpp-0.1.0-RC1> 
> The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186> 
> * 
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
>  
> >
>  
> * 
> https://github.com/apache/nifi-minifi-cpp/commit/bd963503586aeb9b24b4ad5a96da9a1a6818a186
>  
> >
>  
> 
> Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:> 
> MD5: a7155f53d86ef93e37bf28d6e4a0299f> 
> SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd> 
> SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d47b66> 
> 
> 
> Release artifacts are signed with the following key:> 
> https://people.apache.org/keys/committer/aldrin 
> > 
> 
> KEYS file available here:> 
> https://dist.apache.org/repos/dist/release/nifi/KEYS 
> > 
> 
> 15 issues were closed/resolved for this release:> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338046=12319921
>  
> >
>  
> 
> Release note highlights can be found here:> 
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.1.0
>  
> >
>  
> 
> The vote will be open for 72 hours.> 
> Please download the release candidate and evaluate the necessary items> 
> including checking hashes, signatures, build from source, and test. Then> 
> please vote:> 
> 
> [ ] +1 Release this package as nifi-minifi-cpp-0.1.0> 
> [ ] +0 no opinion> 
> [ ] -1 Do not release this package because...> 
>

+1

[Ben Qiu]

+1


On 2016-11-29 10:42 (-0800), Aldrin Piri  wrote:

Hello Apache NiFi community,>


Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.>


# Download latest KEYS file:>

https://dist.apache.org/repos/dist/dev/nifi/KEYS>


# Import keys file:>

gpg --import KEYS>


# Pull down nifi-minifi-cpp-0.1.0 source release artifacts for review:>


wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
>

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
>

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
>

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
>

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
>


# Verify the signature>

gpg --verify nifi-minifi-cpp-0.1.0-source.tar.gz.asc>


# Verify the hashes (md5, sha1, sha256) match the source and what was
provided in the vote email thread>

md5sum nifi-minifi-cpp-0.1.0-source.tar.gz>

sha1sum nifi-minifi-cpp-0.1.0-source.tar.gz>

sha256sum nifi-minifi-cpp-0.1.0-source.tar.gz>


# Untar nifi-minifi-cpp-0.1.0-source.tar.gz>

tar xf nifi-minifi-cpp-0.1.0-source.tar.gz>


# Verify the build works>


Be mindful of the pre-requisites required for the C++ version of MiNiFi,
enumerated in the README and the switching to the CMake build system>

These can vary from system to system and distribution, an example of the
package listing for a recent Ubuntu release is:>

 cmake libboost-dev libxml2-dev libleveldb-dev gcc g++ uuid-dev>


Once the required environment is established, a build can be performed
via:>


cd nifi-minifi-cpp-0.1.0-source>

mkdir build>

cd build>

cmake ..>

make package>


# Verify the contents contain a good README, NOTICE, and LICENSE.>


# Verify the git commit ID is correct>


# Verify the RC was branched off the correct git commit ID>


# Look at the resulting convenience assembly
(nifi-minifi-cpp-0.1.0-bin.tar.gz) found in your build directory>


# Make sure the README, NOTICE, and LICENSE are present and correct>


# Run the resulting convenience binary and make sure it works as expected>


Be mindful of caveats for this initial release, listed in the README.>


For some additional assistance, a package with configuration files for both
a MiNiFI instance and a NiFi instance available at
https://cwiki.apache.org/confluence/display/MINIFI/Releasing+MiNiFi#ReleasingMiNiFi-SampleNiFiandMiNiFiConfigurationtotransmitdatafromMiNiFitoNiFiviaSitetoSite
>

The provided sample configuration bundle assumes that NiFi is configured to
listen on port 8081 and has 10001 configured for Site to Site's
nifi.remote.input.socket.port.>


# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.>


Thank you for your time and effort to validate the release!>

Re: Apache NiFi MiNiFI C++ 0.1.0 Release Helper Guide

[Aldrin Piri]

Hey Bin,

Thanks for voting!

Could you please echo your vote on the VOTE thread?  This helps when the
vote closes to have all items at one link for anyone interested.

Thanks!

On Thu, Dec 1, 2016 at 11:03 AM, Binqiang Qiu  wrote:

> +1
>
> On 2016-11-29 10:42 (-0800), Aldrin Piri  wrote:
> > Hello Apache NiFi community,>
> >
> > Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.>
> >
> > # Download latest KEYS file:>
> > https://dist.apache.org/repos/dist/dev/nifi/KEYS>
> >
> > # Import keys file:>
> > gpg --import KEYS>
> >
> > # Pull down nifi-minifi-cpp-0.1.0 source release artifacts for review:>
> >
> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz>
> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc>
> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5>
> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1>
> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256>
> >
> > # Verify the signature>
> > gpg --verify nifi-minifi-cpp-0.1.0-source.tar.gz.asc>
> >
> > # Verify the hashes (md5, sha1, sha256) match the source and what was
> provided in the vote email thread>
> > md5sum nifi-minifi-cpp-0.1.0-source.tar.gz>
> > sha1sum nifi-minifi-cpp-0.1.0-source.tar.gz>
> > sha256sum nifi-minifi-cpp-0.1.0-source.tar.gz>
> >
> > # Untar nifi-minifi-cpp-0.1.0-source.tar.gz>
> > tar xf nifi-minifi-cpp-0.1.0-source.tar.gz>
> >
> > # Verify the build works>
> >
> > Be mindful of the pre-requisites required for the C++ version of MiNiFi,
> enumerated in the README and the switching to the CMake build system>
> > These can vary from system to system and distribution, an example of the
> package listing for a recent Ubuntu release is:>
> >   cmake libboost-dev libxml2-dev libleveldb-dev gcc g++ uuid-dev>
> >
> > Once the required environment is established, a build can be performed
> via:>
> >
> > cd nifi-minifi-cpp-0.1.0-source>
> > mkdir build>
> > cd build>
> > cmake ..>
> > make package>
> >
> > # Verify the contents contain a good README, NOTICE, and LICENSE.>
> >
> > # Verify the git commit ID is correct>
> >
> > # Verify the RC was branched off the correct git commit ID>
> >
> > # Look at the resulting convenience assembly 
> > (nifi-minifi-cpp-0.1.0-bin.tar.gz)
> found in your build directory>
> >
> > # Make sure the README, NOTICE, and LICENSE are present and correct>
> >
> > # Run the resulting convenience binary and make sure it works as
> expected>
> >
> > Be mindful of caveats for this initial release, listed in the README.>
> >
> > For some additional assistance, a package with configuration files for
> both a MiNiFI instance and a NiFi instance available at
> https://cwiki.apache.org/confluence/display/MINIFI/Releasing+MiNiFi#
> ReleasingMiNiFi-SampleNiFiandMiNiFiConfigurati
> ontotransmitdatafromMiNiFitoNiFiviaSitetoSite>
> > The provided sample configuration bundle assumes that NiFi is configured
> to listen on port 8081 and has 10001 configured for Site to Site's
> nifi.remote.input.socket.port.>
> >
> > # Send a response to the vote thread indicating a +1, 0, -1 based on
> your findings.>
> >
> > Thank you for your time and effort to validate the release!>
> >
> >
>

Re: How to log what flowfile is getting passed out from each Processor

[Bryan Bende]

Hello,

1) There is a LogAttribute processor with a property "Log Payload" which
you can set to true, and you could use this at different points in your
flow.

Another  solution that will work without modifying your flow is to use
NiFi's provenance feature... you can right-click on a processor and select
data provenance, then pick an event and view the lineage graph. From there
you can look at the content of each event in the graph to see how it
changed as it moved through the flow. Very powerful for debugging your flow.

2) You can run as many logical flows as you want in a single NiFi instance.
Typically people organize the top-level canvas using process groups, and
each process group represents a logical flow.

Thanks,

Bryan

On Thu, Dec 1, 2016 at 8:35 AM, srini  wrote:

> Hi,
>
> 1. I want to log what flowfile is getting passed out from each Processor,
> so
> that I can understand what the Processor does on that flowfile.  How to log
> this?
>
> 2. Can I run two flows simultaneously in one nifi environment?
> thanks
> Srini
>
>
>
> --
> View this message in context: http://apache-nifi-developer-
> list.39713.n7.nabble.com/How-to-log-what-flowfile-is-
> getting-passed-out-from-each-Processor-tp14088.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>

Re: Apache NiFi MiNiFI C++ 0.1.0 Release Helper Guide

[Binqiang Qiu]

+1

On 2016-11-29 10:42 (-0800), Aldrin Piri  wrote: 
> Hello Apache NiFi community,> 
> 
> Please find the associated guidance to help those interested in 
> validating/verifying the release so they can vote.> 
> 
> # Download latest KEYS file:> 
> https://dist.apache.org/repos/dist/dev/nifi/KEYS> 
> 
> # Import keys file:> 
> gpg --import KEYS> 
> 
> # Pull down nifi-minifi-cpp-0.1.0 source release artifacts for review:> 
> 
> wget 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz>
>  
> wget 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc>
>  
> wget 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5>
>  
> wget 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1>
>  
> wget 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256>
>  
> 
> # Verify the signature> 
> gpg --verify nifi-minifi-cpp-0.1.0-source.tar.gz.asc> 
> 
> # Verify the hashes (md5, sha1, sha256) match the source and what was 
> provided in the vote email thread> 
> md5sum nifi-minifi-cpp-0.1.0-source.tar.gz> 
> sha1sum nifi-minifi-cpp-0.1.0-source.tar.gz> 
> sha256sum nifi-minifi-cpp-0.1.0-source.tar.gz> 
> 
> # Untar nifi-minifi-cpp-0.1.0-source.tar.gz> 
> tar xf nifi-minifi-cpp-0.1.0-source.tar.gz> 
> 
> # Verify the build works> 
> 
> Be mindful of the pre-requisites required for the C++ version of MiNiFi, 
> enumerated in the README and the switching to the CMake build system> 
> These can vary from system to system and distribution, an example of the 
> package listing for a recent Ubuntu release is:> 
>   cmake libboost-dev libxml2-dev libleveldb-dev gcc g++ uuid-dev> 
> 
> Once the required environment is established, a build can be performed via:> 
> 
> cd nifi-minifi-cpp-0.1.0-source> 
> mkdir build> 
> cd build> 
> cmake ..> 
> make package> 
> 
> # Verify the contents contain a good README, NOTICE, and LICENSE.> 
> 
> # Verify the git commit ID is correct> 
> 
> # Verify the RC was branched off the correct git commit ID> 
> 
> # Look at the resulting convenience assembly 
> (nifi-minifi-cpp-0.1.0-bin.tar.gz) found in your build directory> 
> 
> # Make sure the README, NOTICE, and LICENSE are present and correct> 
> 
> # Run the resulting convenience binary and make sure it works as expected> 
> 
> Be mindful of caveats for this initial release, listed in the README.> 
> 
> For some additional assistance, a package with configuration files for both a 
> MiNiFI instance and a NiFi instance available at 
> https://cwiki.apache.org/confluence/display/MINIFI/Releasing+MiNiFi#ReleasingMiNiFi-SampleNiFiandMiNiFiConfigurationtotransmitdatafromMiNiFitoNiFiviaSitetoSite>
>  
> The provided sample configuration bundle assumes that NiFi is configured to 
> listen on port 8081 and has 10001 configured for Site to Site's 
> nifi.remote.input.socket.port.> 
> 
> # Send a response to the vote thread indicating a +1, 0, -1 based on your 
> findings.> 
> 
> Thank you for your time and effort to validate the release!> 
> 
>

Re: Tika version question

[Joe Witt]

Correct.

Thanks

On Dec 1, 2016 7:56 AM, "Bryan Bende"  wrote:

> Hey Joe,
>
> I believe the issue is that tika-core on its own is fine to use 1.14, but
> tika-parsers is not.
>
> Since standard processors only uses tika-core, that was upgraded to 1.14 so
> that IdentifyMimeType could leverage the newer version, but since the media
> NAR uses core and parsers that wasn't upgraded.
>
> This is my interpretation of:
> https://issues.apache.org/jira/browse/NIFI-2374?focusedCommentId=15669294;
> page=com.atlassian.jira.plugin.system.issuetabpanels:
> comment-tabpanel#comment-15669294
>
> -Bryan
>
>
> On Thu, Dec 1, 2016 at 7:56 AM, Joe Gresock  wrote:
>
> > When looking through some of the poms, I found this comment
> > (nifi-media-processors/pom.xml):
> >
> > 
> > 
> > org.apache.tika
> > tika-core
> > 1.8
> > 
> >
> > However, the same dependency is at version 1.14 in the other poms
> > (nifi-standard-processors and nifi-web-content-viewer).  So my question
> is,
> > is there a license issue with 1.14 or not?  And if not, can we upgrade
> tika
> > in nifi-media-processors?  I know the JSON library license can be used
> > until April, but what about the other part of the comment?
> >
> > Thanks,
> > Joe
> >
> > --
> > I know what it is to be in need, and I know what it is to have plenty.  I
> > have learned the secret of being content in any and every situation,
> > whether well fed or hungry, whether living in plenty or in want.  I can
> do
> > all this through him who gives me strength.*-Philippians 4:12-13*
> >
>

Re: Tika version question

[Bryan Bende]

Hey Joe,

I believe the issue is that tika-core on its own is fine to use 1.14, but
tika-parsers is not.

Since standard processors only uses tika-core, that was upgraded to 1.14 so
that IdentifyMimeType could leverage the newer version, but since the media
NAR uses core and parsers that wasn't upgraded.

This is my interpretation of:
https://issues.apache.org/jira/browse/NIFI-2374?focusedCommentId=15669294=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15669294

-Bryan


On Thu, Dec 1, 2016 at 7:56 AM, Joe Gresock  wrote:

> When looking through some of the poms, I found this comment
> (nifi-media-processors/pom.xml):
>
> 
> 
> org.apache.tika
> tika-core
> 1.8
> 
>
> However, the same dependency is at version 1.14 in the other poms
> (nifi-standard-processors and nifi-web-content-viewer).  So my question is,
> is there a license issue with 1.14 or not?  And if not, can we upgrade tika
> in nifi-media-processors?  I know the JSON library license can be used
> until April, but what about the other part of the comment?
>
> Thanks,
> Joe
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.*-Philippians 4:12-13*
>

How to log what flowfile is getting passed out from each Processor

[srini]

Hi,

1. I want to log what flowfile is getting passed out from each Processor, so
that I can understand what the Processor does on that flowfile.  How to log
this?

2. Can I run two flows simultaneously in one nifi environment? 
thanks
Srini



--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/How-to-log-what-flowfile-is-getting-passed-out-from-each-Processor-tp14088.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Bryan Rosander]

Hey Koji,

As far as I'm aware, minifi-cpp currently supports version 1 of the config
yaml (output by toolkit version 0.0.1).  The toolkit outputs version 2 as
of 0.1.0 (It's not just property names, there are new NiFi features
supported such as process groups, funnels, etc).  We need a way to
communicate this better though.

Thanks,
Bryan

On Thu, Dec 1, 2016 at 4:23 AM, Koji Kawamura 
wrote:

> +1 (non-binding)
>
> Build on RaspberryPi 2 without issue, took (30 - 40 minutes)
> Running sample conf.yml written in README worked without issue
>
> However, when I used minifi-toolkit-0.1.0 (included in MiNiFi java,
> which is under voting, too right now) to convert a NiFi flow template
> to conf.yml. MiNiFi C++ failed to start.
>
> I submitted a JIRA for this. It seems like conf.yml property names are
> not sync up between MiNiFi Java and C++.
> https://issues.apache.org/jira/browse/MINIFI-147
>
> I don't think this issue would be a blocker because it can be
> addressed by modifying the config file manually, but should be noted
> somewhere as a known issue.
>
>
>
> On Thu, Dec 1, 2016 at 7:45 AM, Tony Kurc  wrote:
> > +1 (binding)
> >
> > Build on ubuntu 14.04 without issue (aside from those already mentioned
> > about the dependencies). Ran a simple config without problems. Verified
> > signature and hashes, and reviewed for license issues.
> >
> > Also accidentally verified it does not compile well on g++ 4.8.3
> >
> >
> > On Wed, Nov 30, 2016 at 4:34 PM, Aldrin Piri 
> wrote:
> >
> >> Hey Bryan, thanks for pointing this out.
> >>
> >> Seems this was not updated in the docs with the transition to CMake and
> >> libleveldb was also not captured in the run portion of requirements
> only in
> >> the build.  I've taken note of this and will capture these doc items in
> a
> >> JIRA with any others that 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 
> >> wrote:
> >>
> >> > +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 Tue, Nov 29, 2016 at 9:31 PM, Jeremy Dyer 
> wrote:
> >> >
> >> > > +1 (non-binding) Release this package as nifi-minifi-cpp-0.1.0
> >> > >
> >> > > Validated signature, resulting assembly artifacts, and
> builds/packaging
> >> > for
> >> > > Ubuntu 16.10 and CentOs 7.2. I also validated a simple flow of
> tailing
> >> > > local files and transferring data over site-to-site to NiFi.
> >> > >
> >> > > On Tue, Nov 29, 2016 at 11:54 AM, Aldrin Piri 
> >> wrote:
> >> > >
> >> > > > Hello Apache NiFi Community,
> >> > > >
> >> > > > I am pleased to be calling this vote for the source release of
> Apache
> >> > > NiFi
> >> > > > MiNiFi C++, nifi-minifi-cpp-0.1.0.
> >> > > >
> >> > > > The source archive, signature, and digests can be located at:
> >> > > >
> >> > > > Source Archive:
> >> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
> >> > > > GPG armored signature:
> >> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
> >> > > > Source MD5:
> >> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
> >> > > > Source SHA1:
> >> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
> >> > > > Source SHA256:
> >> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
> >> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
> >> > > >
> >> > > > The Git tag is minifi-cpp-0.1.0-RC1
> >> > > > The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186
> >> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-
> >> > > > cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
> >> > > > * https://github.com/apache/nifi-minifi-cpp/commit/bd9635035
> >> > > > 86aeb9b24b4ad5a96da9a1a6818a186
> >> > > >
> >> > > > Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:
> >> > > > MD5: a7155f53d86ef93e37bf28d6e4a0299f
> >> > > > SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd
> >> > > > SHA256: 62441650684bc2d9631f683b29b3f5
> f12c3c55b8b1f336badf7f7f0061d4
> >> > 7b66
> >> > > >
> >> > > >
> >> > > > Release artifacts are signed with the following key:
> >> > > > https://people.apache.org/keys/committer/aldrin
> >> > > >
> >> > > > KEYS file available 

Tika version question

[Joe Gresock]

When looking through some of the poms, I found this comment
(nifi-media-processors/pom.xml):



org.apache.tika
tika-core
1.8


However, the same dependency is at version 1.14 in the other poms
(nifi-standard-processors and nifi-web-content-viewer).  So my question is,
is there a license issue with 1.14 or not?  And if not, can we upgrade tika
in nifi-media-processors?  I know the JSON library license can be used
until April, but what about the other part of the comment?

Thanks,
Joe

-- 
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.*-Philippians 4:12-13*

Nifi Group Processors Monitoring

[Manee]

Hi Team,

I am working on Nifi Monitoring and Scheduling .In that I am trying to
Find the solution on NiFi Scheduling. How to run processor in single window
and monitoring it and Error should be highlighted as notification.I am stuck
up on to find a solution. please help me out to find a solution  



Thanks,
Manee




-
Thanks,
Manee
--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Group-Processors-Monitoring-tp14083.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.1.0 (RC1)

[Koji Kawamura]

+1 (non-binding)

Build on RaspberryPi 2 without issue, took (30 - 40 minutes)
Running sample conf.yml written in README worked without issue

However, when I used minifi-toolkit-0.1.0 (included in MiNiFi java,
which is under voting, too right now) to convert a NiFi flow template
to conf.yml. MiNiFi C++ failed to start.

I submitted a JIRA for this. It seems like conf.yml property names are
not sync up between MiNiFi Java and C++.
https://issues.apache.org/jira/browse/MINIFI-147

I don't think this issue would be a blocker because it can be
addressed by modifying the config file manually, but should be noted
somewhere as a known issue.



On Thu, Dec 1, 2016 at 7:45 AM, Tony Kurc  wrote:
> +1 (binding)
>
> Build on ubuntu 14.04 without issue (aside from those already mentioned
> about the dependencies). Ran a simple config without problems. Verified
> signature and hashes, and reviewed for license issues.
>
> Also accidentally verified it does not compile well on g++ 4.8.3
>
>
> On Wed, Nov 30, 2016 at 4:34 PM, Aldrin Piri  wrote:
>
>> Hey Bryan, thanks for pointing this out.
>>
>> Seems this was not updated in the docs with the transition to CMake and
>> libleveldb was also not captured in the run portion of requirements only in
>> the build.  I've taken note of this and will capture these doc items in a
>> JIRA with any others that 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 
>> wrote:
>>
>> > +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 Tue, Nov 29, 2016 at 9:31 PM, Jeremy Dyer  wrote:
>> >
>> > > +1 (non-binding) Release this package as nifi-minifi-cpp-0.1.0
>> > >
>> > > Validated signature, resulting assembly artifacts, and builds/packaging
>> > for
>> > > Ubuntu 16.10 and CentOs 7.2. I also validated a simple flow of tailing
>> > > local files and transferring data over site-to-site to NiFi.
>> > >
>> > > On Tue, Nov 29, 2016 at 11:54 AM, Aldrin Piri 
>> wrote:
>> > >
>> > > > Hello Apache NiFi Community,
>> > > >
>> > > > I am pleased to be calling this vote for the source release of Apache
>> > > NiFi
>> > > > MiNiFi C++, nifi-minifi-cpp-0.1.0.
>> > > >
>> > > > The source archive, signature, and digests can be located at:
>> > > >
>> > > > Source Archive:
>> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
>> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz
>> > > > GPG armored signature:
>> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
>> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.asc
>> > > > Source MD5:
>> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
>> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.md5
>> > > > Source SHA1:
>> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
>> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha1
>> > > > Source SHA256:
>> > > >https://dist.apache.org/repos/dist/dev/nifi/nifi-
>> > > > minifi-cpp/0.1.0/nifi-minifi-cpp-0.1.0-source.tar.gz.sha256
>> > > >
>> > > > The Git tag is minifi-cpp-0.1.0-RC1
>> > > > The Git commit hash is bd963503586aeb9b24b4ad5a96da9a1a6818a186
>> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-
>> > > > cpp.git;a=commit;h=bd963503586aeb9b24b4ad5a96da9a1a6818a186
>> > > > * https://github.com/apache/nifi-minifi-cpp/commit/bd9635035
>> > > > 86aeb9b24b4ad5a96da9a1a6818a186
>> > > >
>> > > > Checksums of nifi-minifi-cpp-0.1.0-source.tar.gz:
>> > > > MD5: a7155f53d86ef93e37bf28d6e4a0299f
>> > > > SHA1: f3cb105584d79f70edbd6e5bc0908be3731263fd
>> > > > SHA256: 62441650684bc2d9631f683b29b3f5f12c3c55b8b1f336badf7f7f0061d4
>> > 7b66
>> > > >
>> > > >
>> > > > Release artifacts are signed with the following key:
>> > > > https://people.apache.org/keys/committer/aldrin
>> > > >
>> > > > KEYS file available here:
>> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
>> > > >
>> > > > 15 issues were closed/resolved for this release:
>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
>> > > > on=12338046=12319921
>> > > >
>> > > > Release note highlights can be found here:
>> > > > https://cwiki.apache.org/confluence/display/MINIFI/Release+
>> > > > Notes#ReleaseNotes-Versioncpp-0.1.0
>> > > >
>> > > > The vote will be open for 72 hours.
>> > > > Please download the release candidate and evaluate the necessary
>> items
>> > > > including checking hashes, signatures, build from source, and test.
>> > Then
>> > > > please vote: