Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (binding) went through helper with clean mvn repo, everything checks out and built beautifully On Thu, Mar 14, 2019 at 9:27 PM Koji Kawamura wrote: > +1 binding > > Went through release helper guide. > Thanks Joe for managing this release! > > On Fri, Mar 15, 2019 at 9:34 AM Aldrin Piri wrote: > > > > +1, binding > > > > comments: > > hashes and signature looked good > > build, tests, and contrib check good on Ubuntu and MacOS > > > > > > On Thu, Mar 14, 2019 at 6:58 PM James Wing wrote: > > > > > +1 (binding) - Ran through the release helper, checked the signatures, > > > license/readme, and ran the full build. Ran a simple test flow. > > > > > > Thanks, Joe, for putting this release together! > > > > > > On Tue, Mar 12, 2019 at 10:49 PM Joe Witt wrote: > > > > > > > Hello, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi > > > > 1.9.1. > > > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1138 > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > > > > > > > The Git tag is nifi-1.9.1-RC1 > > > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > > > Checksums of nifi-1.9.1-source-release.zip: > > > > SHA256: > 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > > > > SHA512: > > > > > > > > > > > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > > > > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > > > KEYS file available here: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > 19 issues were closed/resolved for this release: > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > > > > > > > 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-1.9.1 > > > > [ ] +0 no opinion > > > > [ ] -1 Do not release this package because... > > > > > > > >
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 binding Went through release helper guide. Thanks Joe for managing this release! On Fri, Mar 15, 2019 at 9:34 AM Aldrin Piri wrote: > > +1, binding > > comments: > hashes and signature looked good > build, tests, and contrib check good on Ubuntu and MacOS > > > On Thu, Mar 14, 2019 at 6:58 PM James Wing wrote: > > > +1 (binding) - Ran through the release helper, checked the signatures, > > license/readme, and ran the full build. Ran a simple test flow. > > > > Thanks, Joe, for putting this release together! > > > > On Tue, Mar 12, 2019 at 10:49 PM Joe Witt wrote: > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > 1.9.1. > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > https://repository.apache.org/content/repositories/orgapachenifi-1138 > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > > > > > The Git tag is nifi-1.9.1-RC1 > > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > Checksums of nifi-1.9.1-source-release.zip: > > > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > > > SHA512: > > > > > > > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 19 issues were closed/resolved for this release: > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > > > > > Release note highlights can be found here: > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > > > > > 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-1.9.1 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > > >
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1, binding comments: hashes and signature looked good build, tests, and contrib check good on Ubuntu and MacOS On Thu, Mar 14, 2019 at 6:58 PM James Wing wrote: > +1 (binding) - Ran through the release helper, checked the signatures, > license/readme, and ran the full build. Ran a simple test flow. > > Thanks, Joe, for putting this release together! > > On Tue, Mar 12, 2019 at 10:49 PM Joe Witt wrote: > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.9.1. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1138 > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > > > The Git tag is nifi-1.9.1-RC1 > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > Checksums of nifi-1.9.1-source-release.zip: > > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > > SHA512: > > > > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/joewitt.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 19 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > > > 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-1.9.1 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > >
Re: Question about ListFile Test
I've seen similar issues building locally on OSx. I tried going back and
building 1.8.0 and saw similar behavior as master.
Haven't been able to sort it out yet though.
Thanks,
Bryan
On Thu, Mar 14, 2019 at 6:41 PM Ryan Withers wrote:
> Hello all,
>
> I'm encountering an error in the TestListFile.java class and in the
> testFilterAge() specifically. This unit test and associated class can be
> found in the Nifi-Standard-Bundle. I've noticed a couple issues have been
> reported on ListFile before. My issue is most closely related to this one:
> https://issues.apache.org/jira/browse/NIFI-3831, although it may be an
> issue altogether separate. I have never seen this particular test pass
> before and I've attempted building several versions of nifi now.
>
> I'm doing the nifi build on a new model mac. My OS Version is:
>
> 18.2.0 Darwin Kernel Version 18.2.0: Fri Oct 5 19:41:49 PDT 2018;
> root:xnu-4903.221.2~2/RELEASE_X86_64 x86_64
>
> I noticed that my root file system is apfs via mount -v */dev/disk1s1 on /
> (apfs, local, journaled)*
>
> In looking at the ListFiles.testFilterAge() and related methods I found a
> comment above the getTestModifiedTime talking about hfs+ only having
> granularity to one second. For APFS this no longer seems to be the case
> based on the the link tagged below. I've modified this method removing the
> minus 1 and it doesn't seem to have any affect on the failures I get.
>
> /*
> * HFS+, default for OS X, only has granularity to one second,
> accordingly, we go back in time to establish consistent test cases
> *
> * Provides "now" minus 1 second in millis
> */
> private static long getTestModifiedTime() {
> final long nowMillis = System.currentTimeMillis();
> // Subtract a second to avoid possible rounding issues
> final long nowSeconds = TimeUnit.SECONDS.convert(nowMillis,
> TimeUnit.MILLISECONDS) - 1;
> return TimeUnit.MILLISECONDS.convert(nowSeconds, TimeUnit.SECONDS);
> }
>
> https://www.gillware.com/data-recovery-lab/apfs-apple-file-system/
> "Namely, APFS addresses file checksum, nanosecond time stamps, volume
> snapshots, and other features which were lacking under HFS+."
>
> All the file ranges seem shifted, but I'm surprised that nobody else has
> encountered this same issue. I haven't raised this issue as a story yet
> because no one else has noticed the same problem.
>
> In trying to gain additional understanding I've been modifying the unit
> test for testFilterAge and I found incrementing the boundaries by one time
> range unit has allowed me to build a passing test case.
>
> // exclude oldest
> runner.setProperty(ListFile.MIN_AGE, age0);
> -runner.setProperty(ListFile.MAX_AGE, age3);
> +runner.setProperty(ListFile.MAX_AGE, age4);
> runNext.apply(true);
> runner.assertAllFlowFilesTransferred(ListFile.REL_SUCCESS);
> final List successFiles2 =
> runner.getFlowFilesForRelationship(ListFile.REL_SUCCESS);
> @@ -362,7 +362,7 @@ public class TestListFile {
> assertEquals(file1.getName(),
> successFiles2.get(1).getAttribute("filename"));
>
> // exclude newest
> -runner.setProperty(ListFile.MIN_AGE, age1);
> +runner.setProperty(ListFile.MIN_AGE, age2);
> runner.setProperty(ListFile.MAX_AGE, age5);
> runNext.apply(true);
> runner.assertAllFlowFilesTransferred(ListFile.REL_SUCCESS);
> @@ -372,8 +372,8 @@ public class TestListFile {
> assertEquals(file2.getName(),
> successFiles3.get(1).getAttribute("filename"));
>
> // exclude oldest and newest
> -runner.setProperty(ListFile.MIN_AGE, age1);
> -runner.setProperty(ListFile.MAX_AGE, age3);
> +runner.setProperty(ListFile.MIN_AGE, age2);
> +runner.setProperty(ListFile.MAX_AGE, age4);
> runNext.apply(true);
> runner.assertAllFlowFilesTransferred(ListFile.REL_SUCCESS);
> final List successFiles4 =
> runner.getFlowFilesForRelationship(ListFile.REL_SUCCESS);
>
> Has anyone else encountered this? Are there special platform specific
> flags I need to pass when running on a mac? It makes me wonder if the
> generated timing is conflicting with the following line in ListFile.java
>
> final long fileAge = System.currentTimeMillis() -
> attributes.lastModifiedTime().toMillis();
>
>
> That line can be found on line 622 in the ListFile class in the
> createFileFilter method. I'm thinking that utilizing
> System.currentTImeMillis() instead of providing some kind of shim where the
> current clock time can be reliably mocked is causing some inconsistencies
> here. I'm not 100% confident in this because I would think that others
> would be encountering the same or similar issues.
>
> Any help would be greatly appreciated. I'm also happy to clarify if
> anything seems unclear.
>
> Thanks in advance,
>
> --
> Ryan Withers
> Senior Software Developer / Analyst
>
> http://www.linkedin.com/in/ryanwithers
>
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (binding) - Ran through the release helper, checked the signatures, license/readme, and ran the full build. Ran a simple test flow. Thanks, Joe, for putting this release together! On Tue, Mar 12, 2019 at 10:49 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.9.1. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1138 > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > The Git tag is nifi-1.9.1-RC1 > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > Checksums of nifi-1.9.1-source-release.zip: > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > SHA512: > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/joewitt.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 19 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > 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-1.9.1 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Question about ListFile Test
Hello all,
I'm encountering an error in the TestListFile.java class and in the
testFilterAge() specifically. This unit test and associated class can be
found in the Nifi-Standard-Bundle. I've noticed a couple issues have been
reported on ListFile before. My issue is most closely related to this one:
https://issues.apache.org/jira/browse/NIFI-3831, although it may be an
issue altogether separate. I have never seen this particular test pass
before and I've attempted building several versions of nifi now.
I'm doing the nifi build on a new model mac. My OS Version is:
18.2.0 Darwin Kernel Version 18.2.0: Fri Oct 5 19:41:49 PDT 2018;
root:xnu-4903.221.2~2/RELEASE_X86_64 x86_64
I noticed that my root file system is apfs via mount -v */dev/disk1s1 on /
(apfs, local, journaled)*
In looking at the ListFiles.testFilterAge() and related methods I found a
comment above the getTestModifiedTime talking about hfs+ only having
granularity to one second. For APFS this no longer seems to be the case
based on the the link tagged below. I've modified this method removing the
minus 1 and it doesn't seem to have any affect on the failures I get.
/*
* HFS+, default for OS X, only has granularity to one second,
accordingly, we go back in time to establish consistent test cases
*
* Provides "now" minus 1 second in millis
*/
private static long getTestModifiedTime() {
final long nowMillis = System.currentTimeMillis();
// Subtract a second to avoid possible rounding issues
final long nowSeconds = TimeUnit.SECONDS.convert(nowMillis,
TimeUnit.MILLISECONDS) - 1;
return TimeUnit.MILLISECONDS.convert(nowSeconds, TimeUnit.SECONDS);
}
https://www.gillware.com/data-recovery-lab/apfs-apple-file-system/
"Namely, APFS addresses file checksum, nanosecond time stamps, volume
snapshots, and other features which were lacking under HFS+."
All the file ranges seem shifted, but I'm surprised that nobody else has
encountered this same issue. I haven't raised this issue as a story yet
because no one else has noticed the same problem.
In trying to gain additional understanding I've been modifying the unit
test for testFilterAge and I found incrementing the boundaries by one time
range unit has allowed me to build a passing test case.
// exclude oldest
runner.setProperty(ListFile.MIN_AGE, age0);
-runner.setProperty(ListFile.MAX_AGE, age3);
+runner.setProperty(ListFile.MAX_AGE, age4);
runNext.apply(true);
runner.assertAllFlowFilesTransferred(ListFile.REL_SUCCESS);
final List successFiles2 =
runner.getFlowFilesForRelationship(ListFile.REL_SUCCESS);
@@ -362,7 +362,7 @@ public class TestListFile {
assertEquals(file1.getName(),
successFiles2.get(1).getAttribute("filename"));
// exclude newest
-runner.setProperty(ListFile.MIN_AGE, age1);
+runner.setProperty(ListFile.MIN_AGE, age2);
runner.setProperty(ListFile.MAX_AGE, age5);
runNext.apply(true);
runner.assertAllFlowFilesTransferred(ListFile.REL_SUCCESS);
@@ -372,8 +372,8 @@ public class TestListFile {
assertEquals(file2.getName(),
successFiles3.get(1).getAttribute("filename"));
// exclude oldest and newest
-runner.setProperty(ListFile.MIN_AGE, age1);
-runner.setProperty(ListFile.MAX_AGE, age3);
+runner.setProperty(ListFile.MIN_AGE, age2);
+runner.setProperty(ListFile.MAX_AGE, age4);
runNext.apply(true);
runner.assertAllFlowFilesTransferred(ListFile.REL_SUCCESS);
final List successFiles4 =
runner.getFlowFilesForRelationship(ListFile.REL_SUCCESS);
Has anyone else encountered this? Are there special platform specific
flags I need to pass when running on a mac? It makes me wonder if the
generated timing is conflicting with the following line in ListFile.java
final long fileAge = System.currentTimeMillis() -
attributes.lastModifiedTime().toMillis();
That line can be found on line 622 in the ListFile class in the
createFileFilter method. I'm thinking that utilizing
System.currentTImeMillis() instead of providing some kind of shim where the
current clock time can be reliably mocked is causing some inconsistencies
here. I'm not 100% confident in this because I would think that others
would be encountering the same or similar issues.
Any help would be greatly appreciated. I'm also happy to clarify if
anything seems unclear.
Thanks in advance,
--
Ryan Withers
Senior Software Developer / Analyst
http://www.linkedin.com/in/ryanwithers
Re: Configuration Service
This original thread was from quite a long time ago, and there have been many improvements since then, one of which is a variable registry that is exposed directly through the UI [1] and does not require bouncing the NiFi instance. [1] https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#Variables_Window On Thu, Mar 14, 2019 at 6:51 AM Abhay Pasad wrote: > > One of the major issues with an external variable registry file which we > refer to in the nifi.properties file is that it needs NiFi instance to be > bounced. While this may serve your purpose in the lower environments in a > purpose, at an enterprise level cluster this might not be feasible in higher > environments like Production. What this also means is that due to lack of > common global variables/parameters, you may need to spin up a new controller > service every time. I think a Configuration service is a must and should be > worked upon. :) > > > > -- > Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (binding) Ran through the steps in the release helper guide and verified that NIFI-6108 is fixed in this release. Thanks again for RM'ing, Joe. Kevin On Thu, Mar 14, 2019 at 11:41 AM Laszlo Horvath wrote: > > +1 (non-binding) > > - Verified signature > - Verified hashes > - Verified the build, tests were successful > - Verified Git commit ID > - Binary starts as expected > > Laszlo > > > On Thu, Mar 14, 2019 at 3:43 PM Andrew Lim > wrote: > > > +1 (non-binding) > > > > -Ran full clean install on OS X (10.14.2) > > -Ran some simple flows successfully > > -Reviewed documentation updates > > > > Drew > > > > > On Mar 13, 2019, at 1:49 AM, Joe Witt wrote: > > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > 1.9.1. > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > https://repository.apache.org/content/repositories/orgapachenifi-1138 > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > > > > > The Git tag is nifi-1.9.1-RC1 > > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > Checksums of nifi-1.9.1-source-release.zip: > > > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > > > SHA512: > > > > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 19 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > > > > > 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-1.9.1 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > >
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (non-binding) - Verified signature - Verified hashes - Verified the build, tests were successful - Verified Git commit ID - Binary starts as expected Laszlo On Thu, Mar 14, 2019 at 3:43 PM Andrew Lim wrote: > +1 (non-binding) > > -Ran full clean install on OS X (10.14.2) > -Ran some simple flows successfully > -Reviewed documentation updates > > Drew > > > On Mar 13, 2019, at 1:49 AM, Joe Witt wrote: > > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > 1.9.1. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1138 > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > > > The Git tag is nifi-1.9.1-RC1 > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > Checksums of nifi-1.9.1-source-release.zip: > > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > > SHA512: > > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/joewitt.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 19 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > > > Release note highlights can be found here: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > > > 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-1.9.1 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > >
Re: Docker build broken for me in 1.9.1RC2
Agree we should probably update master to use the latest plugin.
For what it's worth, on the RC, I ran this and both completed fine:
mvn -T 2 install -Pcontrib-check,include-grpc,include-atlas
mvn install -Pdocker -DskiptTests -pl nifi-docker/dockermaven
I am logged into dockerhub.
On Thu, Mar 14, 2019 at 11:08 AM Otto Fowler wrote:
>
> Maybe we should update to the latest dockerfile-maven-plugin
>
>
> On March 14, 2019 at 10:49:39, Otto Fowler (ottobackwa...@gmail.com) wrote:
>
> Logging into docker hub got me past that issue
>
>
> On March 14, 2019 at 10:46:00, Otto Fowler (ottobackwa...@gmail.com) wrote:
>
> https://github.com/spotify/docker-maven-plugin/issues/350 maybe?
>
> I will try logging into docker hub and see
>
>
> On March 14, 2019 at 10:43:22, Otto Fowler (ottobackwa...@gmail.com) wrote:
>
> I got the same error after resume
>
>
> On March 14, 2019 at 10:42:05, Otto Fowler (ottobackwa...@gmail.com) wrote:
>
> [ERROR] Failed to execute goal
> com.spotify:dockerfile-maven-plugin:1.3.5:build (default) on project
> nifi-toolkit-assembly: Could not build image:
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
> Can not construct instance of
> com.spotify.docker.client.messages.RegistryAuth: no String-argument
> constructor/factory method to deserialize from String value ('swarm')
> [ERROR] at [Source: N/A; line: -1, column: -1] (through reference chain:
> java.util.LinkedHashMap["stackOrchestrator"])
> [ERROR] -> [Help 1]
>
> I’ll try the resume as well
>
>
> On March 14, 2019 at 10:12:57, Aldrin Piri (aldrinp...@gmail.com) wrote:
>
> Interestingly enough, I had started another build from where that one
> failed using resume from. That worked and generated the images which seems
> to function appropriately. Gives a bit more credence to the possible
> naughtiness on the behalf of the plugin.
>
> On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
>
> > That is interesting. Seems like the plugin may possibly be doing
> > mischievous things with how it handles some of our libraries in the
> > associated build context. Several of these libs, presumably, are also
> > those we adjusted in NIFI recently.
> >
> > I think this is okay to adjust after the release as this shouldn't
> > preclude us from having a Docker image given its reliance only on a
> > successful assembly from the RC process. However, I do also see issue in
> > the build with the profile activated.
> >
> > On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> > wrote:
> >
> >> mvn clean install -Pdocker
> >>
> >> Throws the following error:
> >>
> >> [WARNING] An attempt failed, will retry 1 more times
> >> org.apache.maven.plugin.MojoExecutionException: Could not build image
> >> at
> >> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
> >> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
> >> at
> >>
> >>
> com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
> >> at
> >>
> >>
> com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
> >> at
> >>
> >>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> >> at
> >>
> >>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >> at
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:498)
> >> at
> >>
> >>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> >> at
> >>
> >>
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> >> at
> >>
> >>
> org.codehaus.plexu
Re: Docker build broken for me in 1.9.1RC2
Maybe we should update to the latest dockerfile-maven-plugin
On March 14, 2019 at 10:49:39, Otto Fowler (ottobackwa...@gmail.com) wrote:
Logging into docker hub got me past that issue
On March 14, 2019 at 10:46:00, Otto Fowler (ottobackwa...@gmail.com) wrote:
https://github.com/spotify/docker-maven-plugin/issues/350 maybe?
I will try logging into docker hub and see
On March 14, 2019 at 10:43:22, Otto Fowler (ottobackwa...@gmail.com) wrote:
I got the same error after resume
On March 14, 2019 at 10:42:05, Otto Fowler (ottobackwa...@gmail.com) wrote:
[ERROR] Failed to execute goal
com.spotify:dockerfile-maven-plugin:1.3.5:build (default) on project
nifi-toolkit-assembly: Could not build image:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
[ERROR] at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
[ERROR] -> [Help 1]
I’ll try the resume as well
On March 14, 2019 at 10:12:57, Aldrin Piri (aldrinp...@gmail.com) wrote:
Interestingly enough, I had started another build from where that one
failed using resume from. That worked and generated the images which seems
to function appropriately. Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.
On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
> That is interesting. Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context. Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process. However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>>
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>>
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator
Re: Docker build broken for me in 1.9.1RC2
Logging into docker hub got me past that issue
On March 14, 2019 at 10:46:00, Otto Fowler (ottobackwa...@gmail.com) wrote:
https://github.com/spotify/docker-maven-plugin/issues/350 maybe?
I will try logging into docker hub and see
On March 14, 2019 at 10:43:22, Otto Fowler (ottobackwa...@gmail.com) wrote:
I got the same error after resume
On March 14, 2019 at 10:42:05, Otto Fowler (ottobackwa...@gmail.com) wrote:
[ERROR] Failed to execute goal
com.spotify:dockerfile-maven-plugin:1.3.5:build (default) on project
nifi-toolkit-assembly: Could not build image:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
[ERROR] at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
[ERROR] -> [Help 1]
I’ll try the resume as well
On March 14, 2019 at 10:12:57, Aldrin Piri (aldrinp...@gmail.com) wrote:
Interestingly enough, I had started another build from where that one
failed using resume from. That worked and generated the images which seems
to function appropriately. Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.
On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
> That is interesting. Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context. Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process. However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>>
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>>
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>>
com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
>> at
>>
Re: Docker build broken for me in 1.9.1RC2
https://github.com/spotify/docker-maven-plugin/issues/350 maybe?
I will try logging into docker hub and see
On March 14, 2019 at 10:43:22, Otto Fowler (ottobackwa...@gmail.com) wrote:
I got the same error after resume
On March 14, 2019 at 10:42:05, Otto Fowler (ottobackwa...@gmail.com) wrote:
[ERROR] Failed to execute goal
com.spotify:dockerfile-maven-plugin:1.3.5:build (default) on project
nifi-toolkit-assembly: Could not build image:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
[ERROR] at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
[ERROR] -> [Help 1]
I’ll try the resume as well
On March 14, 2019 at 10:12:57, Aldrin Piri (aldrinp...@gmail.com) wrote:
Interestingly enough, I had started another build from where that one
failed using resume from. That worked and generated the images which seems
to function appropriately. Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.
On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
> That is interesting. Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context. Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process. However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>>
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>>
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>>
com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
>> at
>>
>>
com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
>> at
>>
>>
com.s
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (non-binding) -Ran full clean install on OS X (10.14.2) -Ran some simple flows successfully -Reviewed documentation updates Drew > On Mar 13, 2019, at 1:49 AM, Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.9.1. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1138 > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > The Git tag is nifi-1.9.1-RC1 > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > Checksums of nifi-1.9.1-source-release.zip: > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > SHA512: > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/joewitt.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 19 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > 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-1.9.1 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: Docker build broken for me in 1.9.1RC2
I got the same error after resume
On March 14, 2019 at 10:42:05, Otto Fowler (ottobackwa...@gmail.com) wrote:
[ERROR] Failed to execute goal
com.spotify:dockerfile-maven-plugin:1.3.5:build (default) on project
nifi-toolkit-assembly: Could not build image:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
[ERROR] at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
[ERROR] -> [Help 1]
I’ll try the resume as well
On March 14, 2019 at 10:12:57, Aldrin Piri (aldrinp...@gmail.com) wrote:
Interestingly enough, I had started another build from where that one
failed using resume from. That worked and generated the images which seems
to function appropriately. Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.
On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
> That is interesting. Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context. Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process. However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>>
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>>
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>>
com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
>> at
>>
>>
com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
>> at
>>
>>
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
>> at
>>
>>
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
>> at
>> com.spo
Re: Docker build broken for me in 1.9.1RC2
[ERROR] Failed to execute goal
com.spotify:dockerfile-maven-plugin:1.3.5:build (default) on project
nifi-toolkit-assembly: Could not build image:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
[ERROR] at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
[ERROR] -> [Help 1]
I’ll try the resume as well
On March 14, 2019 at 10:12:57, Aldrin Piri (aldrinp...@gmail.com) wrote:
Interestingly enough, I had started another build from where that one
failed using resume from. That worked and generated the images which seems
to function appropriately. Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.
On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
> That is interesting. Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context. Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process. However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>>
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>>
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>>
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>>
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>>
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>>
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>>
com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
>> at
>>
>>
com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
>> at
>>
>>
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
>> at
>>
>>
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:178)
>> ... 25 more
>> Caused by:
>
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (binding) Ran through release helper and everything looked good, tested a few flows and auto-loading of NARs, worked as expected. On Thu, Mar 14, 2019 at 8:55 AM Mike Thomsen wrote: > > Disregard, I misinterpreted something, but I am having weird local issues > with the maven docker plugin crapping out on me that I normally don't have. > > On Thu, Mar 14, 2019 at 8:52 AM Mike Thomsen wrote: > > > Still trying it out, but the version is 1.9.0 in the Dockerfiles. So > > anyone wanting to test it that way will need a manual patch. > > > > On Wed, Mar 13, 2019 at 11:01 PM Nathan Gough wrote: > > > >> +1 (non-binding) > >> > >> - Verified signature > >> - Verified checksums > >> - mvn contrib executed successfully > >> - Created simple test flow in both standalone and clustered modes, secure > >> and insecure > >> - Checked license and readme files > >> > >> Nathan > >> > >> > >> > >> On Wed, Mar 13, 2019 at 6:33 PM Arpad Boda wrote: > >> > >> > +1 > >> > > >> > -Verified signature > >> > -Verified checksum > >> > -Built, executed tests > >> > -Created a simple flow > >> > -Sent flow files both using raw and HTTP S2S, verified them. > >> > > >> > On 13/03/2019, 22:24, "Rob Fellows" > >> > wrote: > >> > > >> > +1 > >> > > >> > Went through the Release Helper Guide. > >> > Started the app and created a simple data flow. It seemed good to > >> me. > >> > > >> > Thanks, > >> > Rob > >> > > >> > On Wed, Mar 13, 2019 at 3:16 PM Mark Payne > >> > wrote: > >> > > >> > > +1 (binding) > >> > > > >> > > Verified signature, hashes. Build succeeded with contrib-check and > >> > grpc > >> > > profiles. > >> > > Started app and performed some basic functionality testing and all > >> > seemed > >> > > correct. > >> > > > >> > > Thanks > >> > > -Mark > >> > > > >> > > > On Mar 13, 2019, at 1:49 AM, Joe Witt > >> wrote: > >> > > > > >> > > > Hello, > >> > > > > >> > > > I am pleased to be calling this vote for the source release of > >> > Apache > >> > > NiFi > >> > > > 1.9.1. > >> > > > > >> > > > The source zip, including signatures, digests, etc. can be found > >> > at: > >> > > > > >> > https://repository.apache.org/content/repositories/orgapachenifi-1138 > >> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > >> > > > > >> > > > The Git tag is nifi-1.9.1-RC1 > >> > > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > >> > > > > >> > > > >> > > >> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > >> > > > > >> > > > Checksums of nifi-1.9.1-source-release.zip: > >> > > > SHA256: > >> > 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > >> > > > SHA512: > >> > > > > >> > > > >> > > >> 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > >> > > > > >> > > > Release artifacts are signed with the following key: > >> > > > https://people.apache.org/keys/committer/joewitt.asc > >> > > > > >> > > > KEYS file available here: > >> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > >> > > > > >> > > > 19 issues were closed/resolved for this release: > >> > > > > >> > > > >> > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > >> > > > > >> > > > Release note highlights can be found here: > >> > > > > >> > > > >> > > >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > >> > > > > >> > > > 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-1.9.1 > >> > > > [ ] +0 no opinion > >> > > > [ ] -1 Do not release this package because... > >> > > > >> > > > >> > > >> > -- > >> > Thanks, > >> > Rob Fellows > >> > > >> > > >> > > >> > >
Re: Docker build broken for me in 1.9.1RC2
Interestingly enough, I had started another build from where that one
failed using resume from. That worked and generated the images which seems
to function appropriately. Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.
On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri wrote:
> That is interesting. Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context. Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process. However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>> com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>> com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>> com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
>> at
>>
>> com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
>> at
>>
>> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
>> at
>>
>> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:178)
>> ... 25 more
>> Caused by:
>>
>> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>> at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
>>
Re: Docker build broken for me in 1.9.1RC2
That is interesting. Seems like the plugin may possibly be doing
mischievous things with how it handles some of our libraries in the
associated build context. Several of these libs, presumably, are also
those we adjusted in NIFI recently.
I think this is okay to adjust after the release as this shouldn't preclude
us from having a Docker image given its reliance only on a successful
assembly from the RC process. However, I do also see issue in the build
with the profile activated.
On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen wrote:
> mvn clean install -Pdocker
>
> Throws the following error:
>
> [WARNING] An attempt failed, will retry 1 more times
> org.apache.maven.plugin.MojoExecutionException: Could not build image
> at
> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
> at
>
> com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
> at
>
> com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
> at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: com.spotify.docker.client.exceptions.DockerException:
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
> Can not construct instance of
> com.spotify.docker.client.messages.RegistryAuth: no String-argument
> constructor/factory method to deserialize from String value ('swarm')
> at [Source: N/A; line: -1, column: -1] (through reference chain:
> java.util.LinkedHashMap["stackOrchestrator"])
> at
>
> com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
> at
>
> com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
> at
>
> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
> at
>
> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
> at
> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:178)
> ... 25 more
> Caused by:
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
> Can not construct instance of
> com.spotify.docker.client.messages.RegistryAuth: no String-argument
> constructor/factory method to deserialize from String value ('swarm')
> at [Source: N/A; line: -1, column: -1] (through reference chain:
> java.util.LinkedHashMap["stackOrchestrator"])
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:1456)
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.handleMissingInstantiator(DeserializationContext.java:1012)
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.ValueInstantiator._createFromStringFallbac
Re: Docker build broken for me in 1.9.1RC2
You mean RC1?
I’ll try to reproduce
On March 14, 2019 at 09:18:49, Mike Thomsen (mikerthom...@gmail.com) wrote:
mvn clean install -Pdocker
Throws the following error:
[WARNING] An attempt failed, will retry 1 more times
org.apache.maven.plugin.MojoExecutionException: Could not build image
at
com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
at
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
at
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: com.spotify.docker.client.exceptions.DockerException:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
at
com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
at
com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
at
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
at
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
at
com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:178)
... 25 more
Caused by:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:1456)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.handleMissingInstantiator(DeserializationContext.java:1012)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.ValueInstantiator._createFromStringFallbacks(ValueInstantiator.java:370)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.std.StdValueInstantiator.createFromString(StdValueInstantiator.java:315)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromString(BeanDeserializerBase.java:1283)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeOther(BeanDeserializer.java:159)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:150)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.std.MapDeserializer._readAndBindStringKeyMap(MapDeserializer.java:517)
at
com.spotify.docker.c
Docker build broken for me in 1.9.1RC2
mvn clean install -Pdocker
Throws the following error:
[WARNING] An attempt failed, will retry 1 more times
org.apache.maven.plugin.MojoExecutionException: Could not build image
at
com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
at
com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
at
com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: com.spotify.docker.client.exceptions.DockerException:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
at
com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
at
com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
at
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
at
com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
at
com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:178)
... 25 more
Caused by:
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
Can not construct instance of
com.spotify.docker.client.messages.RegistryAuth: no String-argument
constructor/factory method to deserialize from String value ('swarm')
at [Source: N/A; line: -1, column: -1] (through reference chain:
java.util.LinkedHashMap["stackOrchestrator"])
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:1456)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.handleMissingInstantiator(DeserializationContext.java:1012)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.ValueInstantiator._createFromStringFallbacks(ValueInstantiator.java:370)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.std.StdValueInstantiator.createFromString(StdValueInstantiator.java:315)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromString(BeanDeserializerBase.java:1283)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeOther(BeanDeserializer.java:159)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:150)
at
com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.std.MapDeserializer._readAndBindStringKeyMap(MapDeserializer.java:517)
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
Disregard, I misinterpreted something, but I am having weird local issues with the maven docker plugin crapping out on me that I normally don't have. On Thu, Mar 14, 2019 at 8:52 AM Mike Thomsen wrote: > Still trying it out, but the version is 1.9.0 in the Dockerfiles. So > anyone wanting to test it that way will need a manual patch. > > On Wed, Mar 13, 2019 at 11:01 PM Nathan Gough wrote: > >> +1 (non-binding) >> >> - Verified signature >> - Verified checksums >> - mvn contrib executed successfully >> - Created simple test flow in both standalone and clustered modes, secure >> and insecure >> - Checked license and readme files >> >> Nathan >> >> >> >> On Wed, Mar 13, 2019 at 6:33 PM Arpad Boda wrote: >> >> > +1 >> > >> > -Verified signature >> > -Verified checksum >> > -Built, executed tests >> > -Created a simple flow >> > -Sent flow files both using raw and HTTP S2S, verified them. >> > >> > On 13/03/2019, 22:24, "Rob Fellows" >> > wrote: >> > >> > +1 >> > >> > Went through the Release Helper Guide. >> > Started the app and created a simple data flow. It seemed good to >> me. >> > >> > Thanks, >> > Rob >> > >> > On Wed, Mar 13, 2019 at 3:16 PM Mark Payne >> > wrote: >> > >> > > +1 (binding) >> > > >> > > Verified signature, hashes. Build succeeded with contrib-check and >> > grpc >> > > profiles. >> > > Started app and performed some basic functionality testing and all >> > seemed >> > > correct. >> > > >> > > Thanks >> > > -Mark >> > > >> > > > On Mar 13, 2019, at 1:49 AM, Joe Witt >> wrote: >> > > > >> > > > Hello, >> > > > >> > > > I am pleased to be calling this vote for the source release of >> > Apache >> > > NiFi >> > > > 1.9.1. >> > > > >> > > > The source zip, including signatures, digests, etc. can be found >> > at: >> > > > >> > https://repository.apache.org/content/repositories/orgapachenifi-1138 >> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ >> > > > >> > > > The Git tag is nifi-1.9.1-RC1 >> > > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 >> > > > >> > > >> > >> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 >> > > > >> > > > Checksums of nifi-1.9.1-source-release.zip: >> > > > SHA256: >> > 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 >> > > > SHA512: >> > > > >> > > >> > >> 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 >> > > > >> > > > Release artifacts are signed with the following key: >> > > > https://people.apache.org/keys/committer/joewitt.asc >> > > > >> > > > KEYS file available here: >> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS >> > > > >> > > > 19 issues were closed/resolved for this release: >> > > > >> > > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 >> > > > >> > > > Release note highlights can be found here: >> > > > >> > > >> > >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 >> > > > >> > > > 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-1.9.1 >> > > > [ ] +0 no opinion >> > > > [ ] -1 Do not release this package because... >> > > >> > > >> > >> > -- >> > Thanks, >> > Rob Fellows >> > >> > >> > >> >
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
Still trying it out, but the version is 1.9.0 in the Dockerfiles. So anyone wanting to test it that way will need a manual patch. On Wed, Mar 13, 2019 at 11:01 PM Nathan Gough wrote: > +1 (non-binding) > > - Verified signature > - Verified checksums > - mvn contrib executed successfully > - Created simple test flow in both standalone and clustered modes, secure > and insecure > - Checked license and readme files > > Nathan > > > > On Wed, Mar 13, 2019 at 6:33 PM Arpad Boda wrote: > > > +1 > > > > -Verified signature > > -Verified checksum > > -Built, executed tests > > -Created a simple flow > > -Sent flow files both using raw and HTTP S2S, verified them. > > > > On 13/03/2019, 22:24, "Rob Fellows" > > wrote: > > > > +1 > > > > Went through the Release Helper Guide. > > Started the app and created a simple data flow. It seemed good to me. > > > > Thanks, > > Rob > > > > On Wed, Mar 13, 2019 at 3:16 PM Mark Payne > > wrote: > > > > > +1 (binding) > > > > > > Verified signature, hashes. Build succeeded with contrib-check and > > grpc > > > profiles. > > > Started app and performed some basic functionality testing and all > > seemed > > > correct. > > > > > > Thanks > > > -Mark > > > > > > > On Mar 13, 2019, at 1:49 AM, Joe Witt > wrote: > > > > > > > > Hello, > > > > > > > > I am pleased to be calling this vote for the source release of > > Apache > > > NiFi > > > > 1.9.1. > > > > > > > > The source zip, including signatures, digests, etc. can be found > > at: > > > > > > https://repository.apache.org/content/repositories/orgapachenifi-1138 > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ > > > > > > > > The Git tag is nifi-1.9.1-RC1 > > > > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 > > > > > > > > Checksums of nifi-1.9.1-source-release.zip: > > > > SHA256: > > 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 > > > > SHA512: > > > > > > > > > > 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 > > > > > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/joewitt.asc > > > > > > > > KEYS file available here: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > 19 issues were closed/resolved for this release: > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 > > > > > > > > Release note highlights can be found here: > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 > > > > > > > > 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-1.9.1 > > > > [ ] +0 no opinion > > > > [ ] -1 Do not release this package because... > > > > > > > > > > -- > > Thanks, > > Rob Fellows > > > > > > >
Re: [VOTE] Release Apache NiFi 1.9.1 (rc1)
+1 (binding) Verified signature, hashes. Build succeeded with contrib-check Started NiFi up and tested S3 and GCS processors. Also tested auto loading of nars without restart > On Mar 13, 2019, at 11:00 PM, Nathan Gough wrote: > > +1 (non-binding) > > - Verified signature > - Verified checksums > - mvn contrib executed successfully > - Created simple test flow in both standalone and clustered modes, secure > and insecure > - Checked license and readme files > > Nathan > > > > On Wed, Mar 13, 2019 at 6:33 PM Arpad Boda wrote: > >> +1 >> >> -Verified signature >> -Verified checksum >> -Built, executed tests >> -Created a simple flow >> -Sent flow files both using raw and HTTP S2S, verified them. >> >> On 13/03/2019, 22:24, "Rob Fellows" >> wrote: >> >>+1 >> >>Went through the Release Helper Guide. >>Started the app and created a simple data flow. It seemed good to me. >> >>Thanks, >>Rob >> >>On Wed, Mar 13, 2019 at 3:16 PM Mark Payne >> wrote: >> >>> +1 (binding) >>> >>> Verified signature, hashes. Build succeeded with contrib-check and >> grpc >>> profiles. >>> Started app and performed some basic functionality testing and all >> seemed >>> correct. >>> >>> Thanks >>> -Mark >>> On Mar 13, 2019, at 1:49 AM, Joe Witt wrote: Hello, I am pleased to be calling this vote for the source release of >> Apache >>> NiFi 1.9.1. The source zip, including signatures, digests, etc. can be found >> at: >> https://repository.apache.org/content/repositories/orgapachenifi-1138 https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/ The Git tag is nifi-1.9.1-RC1 The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79 >>> >> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79 Checksums of nifi-1.9.1-source-release.zip: SHA256: >> 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38 SHA512: >>> >> 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/joewitt.asc KEYS file available here: https://dist.apache.org/repos/dist/release/nifi/KEYS 19 issues were closed/resolved for this release: >>> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163 Release note highlights can be found here: >>> >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.1 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-1.9.1 [ ] +0 no opinion [ ] -1 Do not release this package because... >>> >>> >> >>-- >>Thanks, >>Rob Fellows >> >> >>
Re: Configuration Service
One of the major issues with an external variable registry file which we refer to in the nifi.properties file is that it needs NiFi instance to be bounced. While this may serve your purpose in the lower environments in a purpose, at an enterprise level cluster this might not be feasible in higher environments like Production. What this also means is that due to lack of common global variables/parameters, you may need to spin up a new controller service every time. I think a Configuration service is a must and should be worked upon. :) -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
