Re: Disable all Remote Processors

2018-06-03 Thread Jorge Machado
Hi Pierre, 

sorry, for the late response. Yes that is the idea. In our case we have a lot 
of RPG and is kind of boring the need to go trough every single one and click 
disable

Thanks for the response any way.




> On 15 May 2018, at 11:50, Pierre Villard  wrote:
> 
> Hi Jorge,
> 
> I'm not sure to understand. You'd like something to disable communication
> on all the RPG included in a PG (recursively I assume)?
> Not sure that's worth a specific API endpoint as I believe this can be
> scripted and done with the currently exposed APIs, no?
> 
> Am I missing something?
> 
> Pierre
> 
> 2018-05-15 9:23 GMT+02:00 Jorge Machado :
> 
>> hi all,
>> 
>> it should be possible to disable all remote processors groups inside a
>> Processor group right ?
>> should we start with a PR for the API ?
>> 
>> Jorge Machado
>> 
>> 
>> 
>> 
>> 
>> 
>> 



Re: Using EL classes with just java Map objects

2018-06-03 Thread Koji Kawamura
Hi Mike,

In order to evaluate an ExpressionLanguage with Map containing
variables, I used Query.prepare, to parse a query String into
PreparedQuery.
Following code snippet works without issue. Is that something you want to do?

final Map map = Collections.singletonMap("name", "John Smith");
final PreparedQuery query = Query.prepare("${name}-${name:length()}");
final String result = query.evaluateExpressions(map, null);
System.out.println(result);

The code prints:
John Smith-10

Thanks,
Koji

On Sun, Jun 3, 2018 at 9:56 AM, Mike Thomsen  wrote:
> Point of clarification, the templated URL would itself be part of the
> coordinate Map, not a descriptor on the service so users would have total
> freedom there to send different variations with each record depending on
> their needs per record being enriched.
>
> On Sat, Jun 2, 2018 at 8:55 PM Mike Thomsen  wrote:
>
>> Ok. That makes sense. The idea was that the RestLookupService would
>> provide a templated URL option so you could specify roughly this as an
>> example:
>>
>> GET "https://something.com:${port}/service/${username}/something/${related
>> }"
>>
>> And have the EL engine take the Map and fill in the blanks.
>>
>> On Sat, Jun 2, 2018 at 6:53 PM Matt Burgess  wrote:
>>
>>> Mike,
>>>
>>> IIRC the "top-level" EL evaluator will go through a string finding EL
>>> constructs and pass them into Query I think.  Also ReplaceText (for
>>> some reason) is the only place I know of where you can quote something
>>> and (if EL is present), the result is treated as a string literal.
>>> Otherwise in NiFi Expression Language I believe a quoted construct on
>>> its own is an attribute to be evaluated. You might want the following:
>>>
>>> literal('${name}-${name:length()}')
>>>
>>> or if that doesn't work, it might be because the Query has to be a
>>> full EL construct so maybe you'd have to put the whole thing together
>>> yourself:
>>>
>>> Query.compile("${name}").evaluate(coordinates) + "-" +
>>> Query.compile("${name:length()}")
>>>
>>> I didn't try this out, and it's very possible my assumptions are not
>>> spot-on, so if these don't work let me know and I'll take a closer
>>> look.
>>>
>>> Regards,
>>> Matt
>>>
>>>
>>>
>>>
>>> On Sat, Jun 2, 2018 at 6:30 PM, Mike Thomsen 
>>> wrote:
>>> > I tried working with the EL package's Query object to try building
>>> > something like this:
>>> >
>>> > def evaluate(String query, Map coordinates) {
>>> > def compiled = Query.compile(query)
>>> > compiled.evaluate(coordinates)
>>> > }
>>> >
>>> > Which for [ name: "John Smith" ] and query '${name}-${name:length()}' I
>>> > expected would return a string with both bracketed operations executed.
>>> It
>>> > threw an exception saying unexpected token '-' at column 7.
>>> >
>>> > Am I missing something here?
>>> >
>>> > Thanks,
>>> >
>>> > Mike
>>>
>>


Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

2018-06-03 Thread Kevin Doran
+1 (non-binding)

I followed the steps in the helper guide and was able to verify the agent works 
as expected with a couple test flows that send data to NiFi over s2s. Most of 
my RC verification was done with the agent on Mac OS 10.12. A full build with 
tests passed on Ubuntu 16.04 for me.

One very minor issue I ran into was a faulty Y/N prompt in bootstrap.sh when 
selecting "N" to bail at the cmake confirmation. It doesn't really do any harm 
as you can easily blow away the build dir and start over, and is an easy fix. I 
filed a JIRA [1] and opened a PR that corrects it [2]. And overall, the 
bootstrap stuff really makes this a lot easier to build and deploy on new 
platforms, so I'm really enjoying using that.

Great work everyone who contributed to the agent since the last release. This 
is a nice step forward! And thanks Jeremy for managing the release!

[1] https://issues.apache.org/jira/browse/MINIFICPP-523
[2] https://github.com/apache/nifi-minifi-cpp/pull/351 

On 5/31/18, 20:39, "Jeremy Dyer"  wrote:

Hello Apache NiFi Community,

I am pleased to call this vote for the source release of Apache NiFi MiNiFi
C++, nifi-minifi-cpp-0.5.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.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz

GPG armored signature:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.asc

Source MD5:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.md5

Source SHA1:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha1

Source SHA256:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha256

The Git tag is minifi-cpp-0.5.0-RC1
The Git commit hash is 5f3b3973e37def4d8ed2753837986d121fd58322
* 
*https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322

*
* 
*https://github.com/apache/nifi-minifi-cpp/commit/5f3b3973e37def4d8ed2753837986d121fd58322

*

Checksums of nifi-minifi-cpp-0.5.0-source.tar.gz:
MD5: 9ec230b9ac3004981000276015860c52
SHA1: a9e3fe34ed25f9f1a840cd318845bcdb6fb622f1
SHA256: 78b5bbd65d1e3484efafc02a882f99063e06b88e1694daff6c24aaa3066037dc

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

87 issues were closed/resolved for this release:

*https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12342659

*

Release note highlights can be found here:

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

*

The vote will close 3 June at 9PM EST.

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.4.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks!





Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

2018-06-03 Thread Tony Kurc
+1 (binding)

-verified signature and hashes
-verified build on a slightly weird ubuntu 16.04 x86_64 (had a tough time
with dependencies, but that was likely my environment). Got about 25%
through a build on a clean Ubuntu MATE 16.04 on a raspberry pi 3, but that
was looking good.
-due to limited time, ran a couple very simple flows
-reviewed LICENSE and NOTICE, saw no issues

On Sun, Jun 3, 2018 at 6:24 PM, Jeremy Dyer  wrote:

> Tony - thanks for trying to verify the release! Always great to have
> people helping out. Your right we do have enough votes for a pass though
> but it's always great to have more feedback in case we missed something.
> Sorry about the equipment failures and let me know if there is anything I
> can o to help
>
> Thanks - Jeremy Dyer
> 
> From: Tony Kurc 
> Sent: Sunday, June 3, 2018 6:02:28 PM
> To: dev@nifi.apache.org
> Subject: Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0
>
> All, I haven't been able to verify this release due to some equipment
> failure.. it looks like there is enough votes to pass, but I'm going to
> keep trying.
>
> On Sun, Jun 3, 2018, 5:58 PM Joe Witt  wrote:
>
> > +1 (binding)
> >
> > Confirmed sigs, hashes, commit.
> > Built on Fedora 28
> > Checked L&N.  Wow that thing is serious!  Nicely done.
> >
> > Ran flow example flow on fedora 28 build against latest nifi using
> > example minificpp flow
> > Ran flow example on osx convenience binary build against latest nifi
> > use example minificpp flow
> >
> > Things look good.
> >
> > Oddity:
> > - Under 'third-party' folder there is an empty 'apache-rat' directory
> >
> > Thanks
> > Joe
> >
> > On Fri, Jun 1, 2018 at 3:43 PM, Aldrin Piri 
> wrote:
> > > +1, binding
> > >
> > > Comments:
> > > * source matched the referenced commit
> > > * L&N look good for the additions since 0.4.0
> > > * hashes and signature looked good
> > > * build and tests checked out in CentOS, OS X 10.13, and Ubuntu 18.04
> > > driven by bootstrap
> > > * verified functionality with some simple flows and Site to Site
> transfer
> > > to NiFi over an extended duration
> > >
> > >
> > > As a note to other reviewers, the resulting assembly will be located in
> > > your build directory as 'nifi-minifi-cpp-0.5.0-bin.tar.gz'
> > >
> > > Thanks for generating this RC, Jeremy and to all the contributors.  A
> lot
> > > of great new bits in this release.
> > >
> > > --aldrin
> > >
> > >
> > > On Fri, Jun 1, 2018 at 11:41 AM, Marc  wrote:
> > >
> > >> Jeremy,
> > >>   +1 binding
> > >>
> > >>   Thanks for generating the release!
> > >>
> > >>I verified sigs and checksums. Built on u18 and OSX.
> > >>
> > >>   I ran unit/integration tests with ctest. Also ran a simple flow with
> > >> GetFile -> LogAttribute, but also includes two controller services for
> > >> battery monitoring and network management.
> > >>
> > >>   Thanks,
> > >>   Marc
> > >>
> > >>
> > >> On Thu, May 31, 2018 at 8:39 PM, Jeremy Dyer 
> > >> wrote:
> > >> > Hello Apache NiFi Community,
> > >> >
> > >> > I am pleased to call this vote for the source release of Apache NiFi
> > >> MiNiFi
> > >> > C++, nifi-minifi-cpp-0.5.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.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz
> > >> >
> > >> > GPG armored signature:
> > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.asc
> > >> >
> > >> > Source MD5:
> > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.md5
> > >> >
> > >> > Source SHA1:
> > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha1
> > >> >
> > >> > Source SHA256:
> > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha256
> > >> >
> > >> > The Git tag is minifi-cpp-0.5.0-RC1
> > >> > The Git commit hash is 5f3b3973e37def4d8ed2753837986d121fd58322
> > >> > * *https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-
> > >> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322
> > >> >  > >> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322>*
> > >> > * *https://github.com/apache/nifi-minifi-cpp/commit/
> > >> 5f3b3973e37def4d8ed2753837986d121fd58322
> > >> >  > >> 5f3b3973e37def4d8ed2753837986d121fd58322>*
> > >> >
> > >> > Checksums of nifi-minifi-cpp-0.5.0-source.tar.gz:
> > >> > MD5: 9ec230b9ac3004981000276015860c52
> > >> > SHA1: a9e3fe34ed25f9f1a840cd318845bcdb6fb622f1
> > >> > SHA256:
> > 78b5bbd65d1e3484efafc02a882f99063e06b88e1694daff6c24aaa3066037dc
> > >> >
> > >> > KEYS file available here:
> > >> > https://dist.apache.org/repos/dist/dev/nifi/KEYS

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

2018-06-03 Thread Jeremy Dyer
Tony - thanks for trying to verify the release! Always great to have people 
helping out. Your right we do have enough votes for a pass though but it's 
always great to have more feedback in case we missed something. Sorry about the 
equipment failures and let me know if there is anything I can o to help

Thanks - Jeremy Dyer

From: Tony Kurc 
Sent: Sunday, June 3, 2018 6:02:28 PM
To: dev@nifi.apache.org
Subject: Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

All, I haven't been able to verify this release due to some equipment
failure.. it looks like there is enough votes to pass, but I'm going to
keep trying.

On Sun, Jun 3, 2018, 5:58 PM Joe Witt  wrote:

> +1 (binding)
>
> Confirmed sigs, hashes, commit.
> Built on Fedora 28
> Checked L&N.  Wow that thing is serious!  Nicely done.
>
> Ran flow example flow on fedora 28 build against latest nifi using
> example minificpp flow
> Ran flow example on osx convenience binary build against latest nifi
> use example minificpp flow
>
> Things look good.
>
> Oddity:
> - Under 'third-party' folder there is an empty 'apache-rat' directory
>
> Thanks
> Joe
>
> On Fri, Jun 1, 2018 at 3:43 PM, Aldrin Piri  wrote:
> > +1, binding
> >
> > Comments:
> > * source matched the referenced commit
> > * L&N look good for the additions since 0.4.0
> > * hashes and signature looked good
> > * build and tests checked out in CentOS, OS X 10.13, and Ubuntu 18.04
> > driven by bootstrap
> > * verified functionality with some simple flows and Site to Site transfer
> > to NiFi over an extended duration
> >
> >
> > As a note to other reviewers, the resulting assembly will be located in
> > your build directory as 'nifi-minifi-cpp-0.5.0-bin.tar.gz'
> >
> > Thanks for generating this RC, Jeremy and to all the contributors.  A lot
> > of great new bits in this release.
> >
> > --aldrin
> >
> >
> > On Fri, Jun 1, 2018 at 11:41 AM, Marc  wrote:
> >
> >> Jeremy,
> >>   +1 binding
> >>
> >>   Thanks for generating the release!
> >>
> >>I verified sigs and checksums. Built on u18 and OSX.
> >>
> >>   I ran unit/integration tests with ctest. Also ran a simple flow with
> >> GetFile -> LogAttribute, but also includes two controller services for
> >> battery monitoring and network management.
> >>
> >>   Thanks,
> >>   Marc
> >>
> >>
> >> On Thu, May 31, 2018 at 8:39 PM, Jeremy Dyer 
> >> wrote:
> >> > Hello Apache NiFi Community,
> >> >
> >> > I am pleased to call this vote for the source release of Apache NiFi
> >> MiNiFi
> >> > C++, nifi-minifi-cpp-0.5.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.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz
> >> >
> >> > GPG armored signature:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.asc
> >> >
> >> > Source MD5:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.md5
> >> >
> >> > Source SHA1:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha1
> >> >
> >> > Source SHA256:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha256
> >> >
> >> > The Git tag is minifi-cpp-0.5.0-RC1
> >> > The Git commit hash is 5f3b3973e37def4d8ed2753837986d121fd58322
> >> > * *https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-
> >> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322
> >> >  >> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322>*
> >> > * *https://github.com/apache/nifi-minifi-cpp/commit/
> >> 5f3b3973e37def4d8ed2753837986d121fd58322
> >> >  >> 5f3b3973e37def4d8ed2753837986d121fd58322>*
> >> >
> >> > Checksums of nifi-minifi-cpp-0.5.0-source.tar.gz:
> >> > MD5: 9ec230b9ac3004981000276015860c52
> >> > SHA1: a9e3fe34ed25f9f1a840cd318845bcdb6fb622f1
> >> > SHA256:
> 78b5bbd65d1e3484efafc02a882f99063e06b88e1694daff6c24aaa3066037dc
> >> >
> >> > KEYS file available here:
> >> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> >> >
> >> > 87 issues were closed/resolved for this release:
> >> > *https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12321520&version=12342659
> >> >  >> projectId=12321520&version=12342659>*
> >> >
> >> > Release note highlights can be found here:
> >> > *https://cwiki.apache.org/confluence/display/MINIFI/
> >> Release+Notes#ReleaseNotes-Versioncpp-0.5.0
> >> >  >> Release+Notes#ReleaseNotes-Versioncpp-0.5.0>*
> >> >
> >> > The vote will close 3 June at 9PM EST.
> >> >
> >> > Please download the release candidate and evaluate the necessary

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

2018-06-03 Thread Tony Kurc
All, I haven't been able to verify this release due to some equipment
failure.. it looks like there is enough votes to pass, but I'm going to
keep trying.

On Sun, Jun 3, 2018, 5:58 PM Joe Witt  wrote:

> +1 (binding)
>
> Confirmed sigs, hashes, commit.
> Built on Fedora 28
> Checked L&N.  Wow that thing is serious!  Nicely done.
>
> Ran flow example flow on fedora 28 build against latest nifi using
> example minificpp flow
> Ran flow example on osx convenience binary build against latest nifi
> use example minificpp flow
>
> Things look good.
>
> Oddity:
> - Under 'third-party' folder there is an empty 'apache-rat' directory
>
> Thanks
> Joe
>
> On Fri, Jun 1, 2018 at 3:43 PM, Aldrin Piri  wrote:
> > +1, binding
> >
> > Comments:
> > * source matched the referenced commit
> > * L&N look good for the additions since 0.4.0
> > * hashes and signature looked good
> > * build and tests checked out in CentOS, OS X 10.13, and Ubuntu 18.04
> > driven by bootstrap
> > * verified functionality with some simple flows and Site to Site transfer
> > to NiFi over an extended duration
> >
> >
> > As a note to other reviewers, the resulting assembly will be located in
> > your build directory as 'nifi-minifi-cpp-0.5.0-bin.tar.gz'
> >
> > Thanks for generating this RC, Jeremy and to all the contributors.  A lot
> > of great new bits in this release.
> >
> > --aldrin
> >
> >
> > On Fri, Jun 1, 2018 at 11:41 AM, Marc  wrote:
> >
> >> Jeremy,
> >>   +1 binding
> >>
> >>   Thanks for generating the release!
> >>
> >>I verified sigs and checksums. Built on u18 and OSX.
> >>
> >>   I ran unit/integration tests with ctest. Also ran a simple flow with
> >> GetFile -> LogAttribute, but also includes two controller services for
> >> battery monitoring and network management.
> >>
> >>   Thanks,
> >>   Marc
> >>
> >>
> >> On Thu, May 31, 2018 at 8:39 PM, Jeremy Dyer 
> >> wrote:
> >> > Hello Apache NiFi Community,
> >> >
> >> > I am pleased to call this vote for the source release of Apache NiFi
> >> MiNiFi
> >> > C++, nifi-minifi-cpp-0.5.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.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz
> >> >
> >> > GPG armored signature:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.asc
> >> >
> >> > Source MD5:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.md5
> >> >
> >> > Source SHA1:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha1
> >> >
> >> > Source SHA256:
> >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> >> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha256
> >> >
> >> > The Git tag is minifi-cpp-0.5.0-RC1
> >> > The Git commit hash is 5f3b3973e37def4d8ed2753837986d121fd58322
> >> > * *https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-
> >> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322
> >> >  >> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322>*
> >> > * *https://github.com/apache/nifi-minifi-cpp/commit/
> >> 5f3b3973e37def4d8ed2753837986d121fd58322
> >> >  >> 5f3b3973e37def4d8ed2753837986d121fd58322>*
> >> >
> >> > Checksums of nifi-minifi-cpp-0.5.0-source.tar.gz:
> >> > MD5: 9ec230b9ac3004981000276015860c52
> >> > SHA1: a9e3fe34ed25f9f1a840cd318845bcdb6fb622f1
> >> > SHA256:
> 78b5bbd65d1e3484efafc02a882f99063e06b88e1694daff6c24aaa3066037dc
> >> >
> >> > KEYS file available here:
> >> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> >> >
> >> > 87 issues were closed/resolved for this release:
> >> > *https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12321520&version=12342659
> >> >  >> projectId=12321520&version=12342659>*
> >> >
> >> > Release note highlights can be found here:
> >> > *https://cwiki.apache.org/confluence/display/MINIFI/
> >> Release+Notes#ReleaseNotes-Versioncpp-0.5.0
> >> >  >> Release+Notes#ReleaseNotes-Versioncpp-0.5.0>*
> >> >
> >> > The vote will close 3 June at 9PM EST.
> >> >
> >> > 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.4.0
> >> > [ ] +0 no opinion
> >> > [ ] -1 Do not release this package because...
> >> >
> >> > Thanks!
> >>
>


Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

2018-06-03 Thread Joe Witt
+1 (binding)

Confirmed sigs, hashes, commit.
Built on Fedora 28
Checked L&N.  Wow that thing is serious!  Nicely done.

Ran flow example flow on fedora 28 build against latest nifi using
example minificpp flow
Ran flow example on osx convenience binary build against latest nifi
use example minificpp flow

Things look good.

Oddity:
- Under 'third-party' folder there is an empty 'apache-rat' directory

Thanks
Joe

On Fri, Jun 1, 2018 at 3:43 PM, Aldrin Piri  wrote:
> +1, binding
>
> Comments:
> * source matched the referenced commit
> * L&N look good for the additions since 0.4.0
> * hashes and signature looked good
> * build and tests checked out in CentOS, OS X 10.13, and Ubuntu 18.04
> driven by bootstrap
> * verified functionality with some simple flows and Site to Site transfer
> to NiFi over an extended duration
>
>
> As a note to other reviewers, the resulting assembly will be located in
> your build directory as 'nifi-minifi-cpp-0.5.0-bin.tar.gz'
>
> Thanks for generating this RC, Jeremy and to all the contributors.  A lot
> of great new bits in this release.
>
> --aldrin
>
>
> On Fri, Jun 1, 2018 at 11:41 AM, Marc  wrote:
>
>> Jeremy,
>>   +1 binding
>>
>>   Thanks for generating the release!
>>
>>I verified sigs and checksums. Built on u18 and OSX.
>>
>>   I ran unit/integration tests with ctest. Also ran a simple flow with
>> GetFile -> LogAttribute, but also includes two controller services for
>> battery monitoring and network management.
>>
>>   Thanks,
>>   Marc
>>
>>
>> On Thu, May 31, 2018 at 8:39 PM, Jeremy Dyer 
>> wrote:
>> > Hello Apache NiFi Community,
>> >
>> > I am pleased to call this vote for the source release of Apache NiFi
>> MiNiFi
>> > C++, nifi-minifi-cpp-0.5.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.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz
>> >
>> > GPG armored signature:
>> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.asc
>> >
>> > Source MD5:
>> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.md5
>> >
>> > Source SHA1:
>> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha1
>> >
>> > Source SHA256:
>> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha256
>> >
>> > The Git tag is minifi-cpp-0.5.0-RC1
>> > The Git commit hash is 5f3b3973e37def4d8ed2753837986d121fd58322
>> > * *https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-
>> cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322
>> > > cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322>*
>> > * *https://github.com/apache/nifi-minifi-cpp/commit/
>> 5f3b3973e37def4d8ed2753837986d121fd58322
>> > > 5f3b3973e37def4d8ed2753837986d121fd58322>*
>> >
>> > Checksums of nifi-minifi-cpp-0.5.0-source.tar.gz:
>> > MD5: 9ec230b9ac3004981000276015860c52
>> > SHA1: a9e3fe34ed25f9f1a840cd318845bcdb6fb622f1
>> > SHA256: 78b5bbd65d1e3484efafc02a882f99063e06b88e1694daff6c24aaa3066037dc
>> >
>> > KEYS file available here:
>> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
>> >
>> > 87 issues were closed/resolved for this release:
>> > *https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12321520&version=12342659
>> > > projectId=12321520&version=12342659>*
>> >
>> > Release note highlights can be found here:
>> > *https://cwiki.apache.org/confluence/display/MINIFI/
>> Release+Notes#ReleaseNotes-Versioncpp-0.5.0
>> > > Release+Notes#ReleaseNotes-Versioncpp-0.5.0>*
>> >
>> > The vote will close 3 June at 9PM EST.
>> >
>> > 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.4.0
>> > [ ] +0 no opinion
>> > [ ] -1 Do not release this package because...
>> >
>> > Thanks!
>>


Re: NIFI URL

2018-06-03 Thread Kevin Doran
Thanks Tony and Chris for the help. I just synced up with Dev on HipChat. For 
those interested, he was running into this issue which was fixed in NiFi 1.5.0: 
https://issues.apache.org/jira/browse/NIFI-4640

Regards,
Kevin

On 6/3/18, 13:52, "Chris Herrera"  wrote:

Dev,
Can you send os/java version. Did you change any parameters? Can you share
the logs from the /logs dir?
Regards,
Chris

On June 3, 2018 at 12:45:58 PM, Tony Kurc (trk...@gmail.com) wrote:

> Hi Dev, I saw your questions in irc, I tried to recommend the dev or user
> list to get a quicker response to your questions, but you had already left
> the channel. I expect your questions will get answered more quickly here
>
> On Sun, Jun 3, 2018, 1:44 PM Dev Lamani  wrote:
>
> Dear Team,
>
> I need urgent help on Apache NIFI.
>
> 1. I could able to install NIFI-1.3.0
>
> 2. Started the NIFI services
>
> 3. Tried Invoking NIFI UI : localhost:8080
>
> Not able to Invoke NIFI UI
> In nifi.properties file the port is 8080.
>
>
>
> Pl help me ASAP.
>
> I was trying to seek help from the nifi chat but nobody responding.
>
> Thanks
> Dev
>
>





Re: NIFI URL

2018-06-03 Thread Chris Herrera
Dev,
Can you send os/java version. Did you change any parameters? Can you share
the logs from the /logs dir?
Regards,
Chris

On June 3, 2018 at 12:45:58 PM, Tony Kurc (trk...@gmail.com) wrote:

> Hi Dev, I saw your questions in irc, I tried to recommend the dev or user
> list to get a quicker response to your questions, but you had already left
> the channel. I expect your questions will get answered more quickly here
>
> On Sun, Jun 3, 2018, 1:44 PM Dev Lamani  wrote:
>
> Dear Team,
>
> I need urgent help on Apache NIFI.
>
> 1. I could able to install NIFI-1.3.0
>
> 2. Started the NIFI services
>
> 3. Tried Invoking NIFI UI : localhost:8080
>
> Not able to Invoke NIFI UI
> In nifi.properties file the port is 8080.
>
>
>
> Pl help me ASAP.
>
> I was trying to seek help from the nifi chat but nobody responding.
>
> Thanks
> Dev
>
>


Re: NIFI URL

2018-06-03 Thread Tony Kurc
Hi Dev, I saw your questions in irc, I tried to recommend the dev or user
list to get a quicker response to your questions, but you had already left
the channel. I expect your questions will get answered more quickly here

On Sun, Jun 3, 2018, 1:44 PM Dev Lamani  wrote:

> Dear Team,
>
> I need urgent help on Apache NIFI.
>
> 1. I could able to install NIFI-1.3.0
>
> 2. Started the NIFI services
>
> 3. Tried Invoking NIFI UI : localhost:8080
>
>   > Not able to Invoke NIFI UI
>   > In nifi.properties file the port is 8080.
>
>
> Pl help me ASAP.
>
> I was trying to seek help from the nifi chat but nobody responding.
>
> Thanks
> Dev
>


NIFI URL

2018-06-03 Thread Dev Lamani
Dear Team,

I need urgent help on Apache NIFI.

1. I could able to install NIFI-1.3.0

2. Started the NIFI services

3. Tried Invoking NIFI UI : localhost:8080

  > Not able to Invoke NIFI UI
  > In nifi.properties file the port is 8080.


Pl help me ASAP.

I was trying to seek help from the nifi chat but nobody responding.

Thanks
Dev


Re: URL configuration for the remote process group in Nifi 1.3

2018-06-03 Thread Mark Payne
Paresh,

When NiFi establishes a connection to the remote instance, it will request 
information from the remote instance about all nodes in the cluster. It then 
persists this information in case nifi is restarted. So whichever node you use 
in your URL is only important for the initial connection. Additionally, NiFi 
will periodically reach out to the remote nifi instances to determine which 
nodes are in the cluster, in case nodes are added to or removed from the 
cluster.

Does that all make sense?

Thanks
-Mark

Sent from my iPhone

> On Jun 3, 2018, at 11:15 AM, Paresh Shah  wrote:
> 
> I have a cluster with 3 nodes. We are using RPG for load balancing
> 
> Node1 ( primary and cluster coordinator ).
> Node2
> Node3
> 
> When configuring the RPG is use Node1 as the target URL. My question is what 
> happens to this RPG when the Node1 goes down or is offline. At this point how 
> does the RPG keep functioning, since we cannot update the URL once its 
> created.
> 
> Thanks
> Paresh
> 


URL configuration for the remote process group in Nifi 1.3

2018-06-03 Thread Paresh Shah
I have a cluster with 3 nodes. We are using RPG for load balancing

Node1 ( primary and cluster coordinator ).
Node2
Node3

When configuring the RPG is use Node1 as the target URL. My question is what 
happens to this RPG when the Node1 goes down or is offline. At this point how 
does the RPG keep functioning, since we cannot update the URL once its created.

Thanks
Paresh