Apache NiFi Community,
I am pleased to announce that the 0.2.0 release of Apache NiFi Registry passes
with:
9 +1 (binding) votes
3 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
Here is the PMC vote thread:
https://lists.apache.
+1 from me as well, having verified the RC according to the steps in the
release helper.
On 6/18/18, 20:03, "James Wing" wrote:
+1 (binding). Ran through the release helper, tested with a NiFi
1.7.0-SNAPSHOT build.
Thanks, Kevin!
On Fri, Jun 15, 2018 at 6:26 PM Kevin
Mike,
No, there's a NullPointerException within groovy-eclipse-compiler during
the test compile phase. Part of what I'm doing is trying to encapsulate
everything into a profile that activates when a version of Java higher than
1.8 is being used to build. I'm not a Maven wizard, but
overriding/ex
Thanks.. I will surely take some time to go through the suggested topics and
then proceed.
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
+1 (binding). Ran through the release helper, tested with a NiFi
1.7.0-SNAPSHOT build.
Thanks, Kevin!
On Fri, Jun 15, 2018 at 6:26 PM Kevin Doran wrote:
> Hello,
>
> I am pleased to call this vote for the source release of Apache NiFi
> Registry 0.2.0.
>
> The source zip, including signatures,
Ah thanks for the heads up Andy. Makes sense. The vote seems to be
going along quite well so this should sort itself out in a couple
hours. Thanks
On Mon, Jun 18, 2018 at 3:51 PM, Andy LoPresto wrote:
> Folks,
>
> As part of the 1.7.0 closeout effort, I accidentally merged PR 2801 [1]
> (Apach
Folks,
As part of the 1.7.0 closeout effort, I accidentally merged PR 2801 [1] (Apache
NiFi Registry 0.2.0 client integration) for NIFI-5319 before the 0.2.0
artifacts are released. The build will work normally for anyone who has done
Registry 0.2.0 RC1 verification, because their local reposit
+1 (binding)
Verified all the typical sig/hash/L&N.
Verified function.
Thanks for RM Kevin!
Joe
On Mon, Jun 18, 2018 at 2:47 PM, Aldrin Piri wrote:
> +1, binding
>
> notes:
> signature and hashes look good
> license and notice looked good excluding those issues already presented
> verified suc
+1, binding
notes:
signature and hashes look good
license and notice looked good excluding those issues already presented
verified successful integration and workflow unsecured with NiFi
On Mon, Jun 18, 2018 at 1:26 PM Scott Aslan wrote:
> +1 binding,
>
> -ran through release helper
> -setup un
+1 binding,
-ran through release helper
-setup unsecured nifi, configured registry 0.2.0, created a bucket, placed
PG's under version control, all looks good
Thanks for RM'ing Kevin!
On Mon, Jun 18, 2018 at 7:10 AM Marc wrote:
> +1 binding..
>
> Stepped through helper guide for verification
I'm guessing they were probably Spock tests. Is that right?
On Mon, Jun 18, 2018 at 3:06 PM Jeff wrote:
> Mike,
>
> I'm working on NIFI-5176 [1] and will try switching to GMavenPlus. I've
> been running into issues with compiling Groovy tests with
> groovy-eclipse-maven, and it'd be nice if swi
Mike,
I'm working on NIFI-5176 [1] and will try switching to GMavenPlus. I've
been running into issues with compiling Groovy tests with
groovy-eclipse-maven, and it'd be nice if switching the plugin would help.
I'll report back with my hopeful success!
[1] https://issues.apache.org/jira/browse/N
Evan,
It looks like you're trying to run NiFi on Java 9, and as Mike pointed out,
you'll want to make sure you're using Java 1.8 with the version in Brew,
though I'm not sure which version is on Brew. I didn't know it was in
there, either. :) When NiFi 1.7.0 is released (with NIFI-5175 [1]), it
s
Dave,
It sounds like many of the issues you are having with specific processors can
be answered with a combination of mailing list questions and the processor
documentation. I would also encourage you to read the Getting Started Guide
[1], User Guide [2], and Admin Guide [3]. They are long, but
Thanks.. I will try to implement this suggestion also.
Actually since I earlier have managed a Datawarehouse project, I am trying
to pick up scenarios based on that experience. I have actually visualised
this specific scenario.
The source file will be a CSV file. And all the fields will be be sto
Thank you.. I will try this and the other solution offered.
Thanks
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Hello,
If you're data is only CSV, you might want to look at ValidateCSV processor.
Using QueryRecord processor would also give you options to validate your
data with your own constraints.
Pierre
2018-06-18 14:52 GMT+02:00 Bryan Bende :
> Hello,
>
> In general you probably want to take a look
Hello,
In general you probably want to take a look at the "record" processors
which will offer a more efficient way of performing this task without
needing to split to 1 message per flow file.
The flow with the record processors would probably be GetFile ->
ConvertRecord (using CsvReader and Avro
+1 binding..
Stepped through helper guide for verification and validation. Looks great!
On Mon, Jun 18, 2018, 4:18 AM Pierre Villard
wrote:
> +1 binding,
>
> - Went through the release helper guide
> - Tested the hook mechanism
>
> All looks good to me. Thanks for the release management Kevin
+1 binding,
- Went through the release helper guide
- Tested the hook mechanism
All looks good to me. Thanks for the release management Kevin and to all
the contributors!
Pierre
2018-06-18 8:05 GMT+02:00 Koji Kawamura :
> +1 (binding)
>
> - Run through Release Helper Guide
> - Tested other dat
Hi all,
A PR is submitted to add to do classification or prediction using a
pre-built model with DeepLearning4J library (thanks @mans2singh!).
https://github.com/apache/nifi/pull/2686
I found following things can/should be improved so that people can use
it easier from a NiFi flow:
- To utilize e
21 matches
Mail list logo
