You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Aldrin Piri <al...@gmail.com> on 2017/05/03 14:55:04 UTC
Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release
Looks like we have one last item scheduled [1] for this release version
with review under way since the last message. We've also uncovered and
remedied a few build and test issues during that same time period which
will make for nice additions. Upon conclusion of the review process for
the remaining item, I will move forward conducting the release.
Thanks!
--aldrin
[1]
https://issues.apache.org/jira/browse/MINIFI-286?jql=fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
On Thu, Apr 13, 2017 at 10:19 AM, Aldrin Piri <al...@gmail.com> wrote:
> Hey folks,
>
> We've had a good bit of progress on MiNiFi C++ and think we have reached a
> point where it makes sense to capture some of the good strides that have
> been made so far and start another release.
>
> There are currently three issues open [1]. Two of which have patches, near
> completion, and the third which may be a candidate for an 0.3.0 target.
>
> I would be happy to carry out release duties unless there are other folks
> that feel so inclined. I have also created a JIRA [2] to aid in tracking
> any additional concerns or dependencies for the process.
>
> Thanks for your consideration!
>
> --aldrin
>
> [1] https://issues.apache.org/jira/browse/MINIFI-227?jql=
> fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> 20BY%20priority%20DESC
> [2] https://issues.apache.org/jira/browse/MINIFI-267
>
Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release
Posted by Aldrin Piri <al...@gmail.com>.
Looks like we have resolved the remaining items. I will start the RC
process and have something out tonight/tomorrow morning.
Thanks!
Aldrin
On Wed, May 3, 2017 at 6:30 PM, Kevin Doran <kd...@gmail.com> wrote:
> Thanks, Aldrin.
>
> PR now open for MINIFI-294
> https://github.com/apache/nifi-minifi-cpp/pull/90
>
> Kevin
>
> On 5/3/17, 17:31, "Aldrin Piri" <al...@gmail.com> wrote:
>
> Kevin,
>
> Thanks for the heads up.
>
> While I started the RM process I also noticed some issues with license
> for
> unused thirdparty modules in one of our thirdparty modules. I have a
> PR
> [1] up for review to fix this as well as the associated JIRA [2].
>
> [1] https://github.com/apache/nifi-minifi-cpp/pull/89
> [2] http://issues.apache.org/jira/browse/MINIFI-293
>
> On Wed, May 3, 2017 at 5:11 PM, Kevin Doran <kd...@gmail.com>
> wrote:
>
> > Hi Aldrin,
> >
> > One other issue came up in testing, which is that using the
> config.yml in
> > the README file throws the following error:
> >
> > HW13384:nifi-minifi-cpp-0.2.0 brosander$ bin/minifi.sh run
> > libc++abi.dylib: terminating with uncaught exception of type
> > YAML::TypedBadConversion<std::__1::basic_string<char,
> > std::__1::char_traits<char>, std::__1::allocator<char> > >: bad
> conversion
> > bin/minifi.sh: line 257: 25630 Abort trap: 6
> ${minifi_executable}
> >
> > This is due to missing “source name” and “destination name” fields in
> > connections, which changes for MINIFI-275 make required fields.
> >
> > I’ve opened a JIRA, MINIFI- 294 [1], to capture the work needed to
> resolve
> > this and am working on it now to include in the cpp-0.2.0 release
> >
> > [1] https://issues.apache.org/jira/browse/MINIFI-294
> >
> > Thanks,
> > Kevin
> >
> > On 5/3/17, 11:10, "Jeremy Dyer" <jd...@gmail.com> wrote:
> >
> > Thanks Aldrin. I'm working on wrapping up that final issue now
> >
> > On Wed, May 3, 2017 at 10:55 AM, Aldrin Piri <
> aldrinpiri@gmail.com>
> > wrote:
> >
> > > Looks like we have one last item scheduled [1] for this release
> > version
> > > with review under way since the last message. We've also
> uncovered
> > and
> > > remedied a few build and test issues during that same time
> period
> > which
> > > will make for nice additions. Upon conclusion of the review
> process
> > for
> > > the remaining item, I will move forward conducting the release.
> > >
> > > Thanks!
> > >
> > > --aldrin
> > >
> > > [1]
> > > https://issues.apache.org/jira/browse/MINIFI-286?jql=
> > > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > 20BY%20priority%20DESC
> > >
> > > On Thu, Apr 13, 2017 at 10:19 AM, Aldrin Piri <
> aldrinpiri@gmail.com>
> > > wrote:
> > >
> > > > Hey folks,
> > > >
> > > > We've had a good bit of progress on MiNiFi C++ and think we
> have
> > reached
> > > a
> > > > point where it makes sense to capture some of the good
> strides
> > that have
> > > > been made so far and start another release.
> > > >
> > > > There are currently three issues open [1]. Two of which have
> > patches,
> > > near
> > > > completion, and the third which may be a candidate for an
> 0.3.0
> > target.
> > > >
> > > > I would be happy to carry out release duties unless there are
> > other folks
> > > > that feel so inclined. I have also created a JIRA [2] to
> aid in
> > tracking
> > > > any additional concerns or dependencies for the process.
> > > >
> > > > Thanks for your consideration!
> > > >
> > > > --aldrin
> > > >
> > > > [1] https://issues.apache.org/jira/browse/MINIFI-227?jql=
> > > > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > > > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > > 20BY%20priority%20DESC
> > > > [2] https://issues.apache.org/jira/browse/MINIFI-267
> > > >
> > >
> >
> >
> >
> >
>
>
>
>
Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release
Posted by Kevin Doran <kd...@gmail.com>.
Thanks, Aldrin.
PR now open for MINIFI-294
https://github.com/apache/nifi-minifi-cpp/pull/90
Kevin
On 5/3/17, 17:31, "Aldrin Piri" <al...@gmail.com> wrote:
Kevin,
Thanks for the heads up.
While I started the RM process I also noticed some issues with license for
unused thirdparty modules in one of our thirdparty modules. I have a PR
[1] up for review to fix this as well as the associated JIRA [2].
[1] https://github.com/apache/nifi-minifi-cpp/pull/89
[2] http://issues.apache.org/jira/browse/MINIFI-293
On Wed, May 3, 2017 at 5:11 PM, Kevin Doran <kd...@gmail.com> wrote:
> Hi Aldrin,
>
> One other issue came up in testing, which is that using the config.yml in
> the README file throws the following error:
>
> HW13384:nifi-minifi-cpp-0.2.0 brosander$ bin/minifi.sh run
> libc++abi.dylib: terminating with uncaught exception of type
> YAML::TypedBadConversion<std::__1::basic_string<char,
> std::__1::char_traits<char>, std::__1::allocator<char> > >: bad conversion
> bin/minifi.sh: line 257: 25630 Abort trap: 6 ${minifi_executable}
>
> This is due to missing “source name” and “destination name” fields in
> connections, which changes for MINIFI-275 make required fields.
>
> I’ve opened a JIRA, MINIFI- 294 [1], to capture the work needed to resolve
> this and am working on it now to include in the cpp-0.2.0 release
>
> [1] https://issues.apache.org/jira/browse/MINIFI-294
>
> Thanks,
> Kevin
>
> On 5/3/17, 11:10, "Jeremy Dyer" <jd...@gmail.com> wrote:
>
> Thanks Aldrin. I'm working on wrapping up that final issue now
>
> On Wed, May 3, 2017 at 10:55 AM, Aldrin Piri <al...@gmail.com>
> wrote:
>
> > Looks like we have one last item scheduled [1] for this release
> version
> > with review under way since the last message. We've also uncovered
> and
> > remedied a few build and test issues during that same time period
> which
> > will make for nice additions. Upon conclusion of the review process
> for
> > the remaining item, I will move forward conducting the release.
> >
> > Thanks!
> >
> > --aldrin
> >
> > [1]
> > https://issues.apache.org/jira/browse/MINIFI-286?jql=
> > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > 20BY%20priority%20DESC
> >
> > On Thu, Apr 13, 2017 at 10:19 AM, Aldrin Piri <al...@gmail.com>
> > wrote:
> >
> > > Hey folks,
> > >
> > > We've had a good bit of progress on MiNiFi C++ and think we have
> reached
> > a
> > > point where it makes sense to capture some of the good strides
> that have
> > > been made so far and start another release.
> > >
> > > There are currently three issues open [1]. Two of which have
> patches,
> > near
> > > completion, and the third which may be a candidate for an 0.3.0
> target.
> > >
> > > I would be happy to carry out release duties unless there are
> other folks
> > > that feel so inclined. I have also created a JIRA [2] to aid in
> tracking
> > > any additional concerns or dependencies for the process.
> > >
> > > Thanks for your consideration!
> > >
> > > --aldrin
> > >
> > > [1] https://issues.apache.org/jira/browse/MINIFI-227?jql=
> > > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > 20BY%20priority%20DESC
> > > [2] https://issues.apache.org/jira/browse/MINIFI-267
> > >
> >
>
>
>
>
Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release
Posted by Aldrin Piri <al...@gmail.com>.
Kevin,
Thanks for the heads up.
While I started the RM process I also noticed some issues with license for
unused thirdparty modules in one of our thirdparty modules. I have a PR
[1] up for review to fix this as well as the associated JIRA [2].
[1] https://github.com/apache/nifi-minifi-cpp/pull/89
[2] http://issues.apache.org/jira/browse/MINIFI-293
On Wed, May 3, 2017 at 5:11 PM, Kevin Doran <kd...@gmail.com> wrote:
> Hi Aldrin,
>
> One other issue came up in testing, which is that using the config.yml in
> the README file throws the following error:
>
> HW13384:nifi-minifi-cpp-0.2.0 brosander$ bin/minifi.sh run
> libc++abi.dylib: terminating with uncaught exception of type
> YAML::TypedBadConversion<std::__1::basic_string<char,
> std::__1::char_traits<char>, std::__1::allocator<char> > >: bad conversion
> bin/minifi.sh: line 257: 25630 Abort trap: 6 ${minifi_executable}
>
> This is due to missing “source name” and “destination name” fields in
> connections, which changes for MINIFI-275 make required fields.
>
> I’ve opened a JIRA, MINIFI- 294 [1], to capture the work needed to resolve
> this and am working on it now to include in the cpp-0.2.0 release
>
> [1] https://issues.apache.org/jira/browse/MINIFI-294
>
> Thanks,
> Kevin
>
> On 5/3/17, 11:10, "Jeremy Dyer" <jd...@gmail.com> wrote:
>
> Thanks Aldrin. I'm working on wrapping up that final issue now
>
> On Wed, May 3, 2017 at 10:55 AM, Aldrin Piri <al...@gmail.com>
> wrote:
>
> > Looks like we have one last item scheduled [1] for this release
> version
> > with review under way since the last message. We've also uncovered
> and
> > remedied a few build and test issues during that same time period
> which
> > will make for nice additions. Upon conclusion of the review process
> for
> > the remaining item, I will move forward conducting the release.
> >
> > Thanks!
> >
> > --aldrin
> >
> > [1]
> > https://issues.apache.org/jira/browse/MINIFI-286?jql=
> > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > 20BY%20priority%20DESC
> >
> > On Thu, Apr 13, 2017 at 10:19 AM, Aldrin Piri <al...@gmail.com>
> > wrote:
> >
> > > Hey folks,
> > >
> > > We've had a good bit of progress on MiNiFi C++ and think we have
> reached
> > a
> > > point where it makes sense to capture some of the good strides
> that have
> > > been made so far and start another release.
> > >
> > > There are currently three issues open [1]. Two of which have
> patches,
> > near
> > > completion, and the third which may be a candidate for an 0.3.0
> target.
> > >
> > > I would be happy to carry out release duties unless there are
> other folks
> > > that feel so inclined. I have also created a JIRA [2] to aid in
> tracking
> > > any additional concerns or dependencies for the process.
> > >
> > > Thanks for your consideration!
> > >
> > > --aldrin
> > >
> > > [1] https://issues.apache.org/jira/browse/MINIFI-227?jql=
> > > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > 20BY%20priority%20DESC
> > > [2] https://issues.apache.org/jira/browse/MINIFI-267
> > >
> >
>
>
>
>
Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release
Posted by Kevin Doran <kd...@gmail.com>.
Hi Aldrin,
One other issue came up in testing, which is that using the config.yml in the README file throws the following error:
HW13384:nifi-minifi-cpp-0.2.0 brosander$ bin/minifi.sh run
libc++abi.dylib: terminating with uncaught exception of type YAML::TypedBadConversion<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >: bad conversion
bin/minifi.sh: line 257: 25630 Abort trap: 6 ${minifi_executable}
This is due to missing “source name” and “destination name” fields in connections, which changes for MINIFI-275 make required fields.
I’ve opened a JIRA, MINIFI- 294 [1], to capture the work needed to resolve this and am working on it now to include in the cpp-0.2.0 release
[1] https://issues.apache.org/jira/browse/MINIFI-294
Thanks,
Kevin
On 5/3/17, 11:10, "Jeremy Dyer" <jd...@gmail.com> wrote:
Thanks Aldrin. I'm working on wrapping up that final issue now
On Wed, May 3, 2017 at 10:55 AM, Aldrin Piri <al...@gmail.com> wrote:
> Looks like we have one last item scheduled [1] for this release version
> with review under way since the last message. We've also uncovered and
> remedied a few build and test issues during that same time period which
> will make for nice additions. Upon conclusion of the review process for
> the remaining item, I will move forward conducting the release.
>
> Thanks!
>
> --aldrin
>
> [1]
> https://issues.apache.org/jira/browse/MINIFI-286?jql=
> fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> 20BY%20priority%20DESC
>
> On Thu, Apr 13, 2017 at 10:19 AM, Aldrin Piri <al...@gmail.com>
> wrote:
>
> > Hey folks,
> >
> > We've had a good bit of progress on MiNiFi C++ and think we have reached
> a
> > point where it makes sense to capture some of the good strides that have
> > been made so far and start another release.
> >
> > There are currently three issues open [1]. Two of which have patches,
> near
> > completion, and the third which may be a candidate for an 0.3.0 target.
> >
> > I would be happy to carry out release duties unless there are other folks
> > that feel so inclined. I have also created a JIRA [2] to aid in tracking
> > any additional concerns or dependencies for the process.
> >
> > Thanks for your consideration!
> >
> > --aldrin
> >
> > [1] https://issues.apache.org/jira/browse/MINIFI-227?jql=
> > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > 20BY%20priority%20DESC
> > [2] https://issues.apache.org/jira/browse/MINIFI-267
> >
>
Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release
Posted by Jeremy Dyer <jd...@gmail.com>.
Thanks Aldrin. I'm working on wrapping up that final issue now
On Wed, May 3, 2017 at 10:55 AM, Aldrin Piri <al...@gmail.com> wrote:
> Looks like we have one last item scheduled [1] for this release version
> with review under way since the last message. We've also uncovered and
> remedied a few build and test issues during that same time period which
> will make for nice additions. Upon conclusion of the review process for
> the remaining item, I will move forward conducting the release.
>
> Thanks!
>
> --aldrin
>
> [1]
> https://issues.apache.org/jira/browse/MINIFI-286?jql=
> fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> 20BY%20priority%20DESC
>
> On Thu, Apr 13, 2017 at 10:19 AM, Aldrin Piri <al...@gmail.com>
> wrote:
>
> > Hey folks,
> >
> > We've had a good bit of progress on MiNiFi C++ and think we have reached
> a
> > point where it makes sense to capture some of the good strides that have
> > been made so far and start another release.
> >
> > There are currently three issues open [1]. Two of which have patches,
> near
> > completion, and the third which may be a candidate for an 0.3.0 target.
> >
> > I would be happy to carry out release duties unless there are other folks
> > that feel so inclined. I have also created a JIRA [2] to aid in tracking
> > any additional concerns or dependencies for the process.
> >
> > Thanks for your consideration!
> >
> > --aldrin
> >
> > [1] https://issues.apache.org/jira/browse/MINIFI-227?jql=
> > fixVersion%20%3D%20cpp-0.2.0%20AND%20project%20%3D%
> > 20MINIFI%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > 20BY%20priority%20DESC
> > [2] https://issues.apache.org/jira/browse/MINIFI-267
> >
>