Forgot to mention, that I recently wrote and deployed a service that uses
that to take POJOs and expose a schema to third party clients that they can
use with the Avro APIs to send valid JSON that can be ingested into our
Kafka queues.
On Mon, Feb 3, 2020 at 6:06 PM Mike Thomsen wrote:
> Hi
Hi Emanuel,
> This may look simple use case, but very hard to implement due.. but please
> do surprise me with sequence of processors needed to implement what i
think
> *its a great real world example of data quality*
I think this is the root of the problem. Personally, I wouldn't
characterize
Mark,
Glad to see that it worked for you. I have more information stashed away
somewhere about how and why IntelliJ IDEA implicitly enables profiles, but
having Java 11 on your system and IDEA knowing about it seems to trigger
the implicit activation of the "jigsaw" profile. You won't have the
Thanks Pierre, seems I already had an account:
username: emanueol
Best Regards,
*Emanuel Oliveira*
On Mon, Feb 3, 2020 at 7:34 PM Pierre Villard
wrote:
> Hi Emanuel,
>
> Just wanted to answer to your questions regarding JIRA. You can create an
> account on the Apache JIRA [1] and open
Apache NiFi Community,
I am pleased to announce that the 1.11.1 release of Apache NiFi passes with
7 +1 (binding) votes
7 +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:
+1 binding
On Mon, Feb 3, 2020 at 3:33 PM Shayne Burgess
wrote:
> +1 (non-binding)
>
> Verified signatures and deploy.
> Created cluster on Azure, deployed flow.
> LGTM
>
> On Mon, Feb 3, 2020 at 12:20 PM Bryan Bende wrote:
>
> > +1 (binding)
> >
> > - Verified signatures, license, notice,
+1 (non-binding)
Verified signatures and deploy.
Created cluster on Azure, deployed flow.
LGTM
On Mon, Feb 3, 2020 at 12:20 PM Bryan Bende wrote:
> +1 (binding)
>
> - Verified signatures, license, notice, README
> - Built on MacOS and ran basic flow
>
> On Mon, Feb 3, 2020 at 1:45 PM Pierre
+1 (binding)
- Verified signatures, license, notice, README
- Built on MacOS and ran basic flow
On Mon, Feb 3, 2020 at 1:45 PM Pierre Villard
wrote:
>
> +1, binding
>
> Verified signatures, built and deployed a secured cluster on GCP, ran some
> flows. LGTM.
>
> Thanks Joe for taking care of
Hi Emanuel,
Just wanted to answer to your questions regarding JIRA. You can create an
account on the Apache JIRA [1] and open JIRAs on the NiFi project [2]. Once
you created an account and logged in the JIRA once, you can share your
login with us, and we can grant you the "contributor" role which
Hi Mike,
Let me summarize as i see my long post is not pads ng the clean easy
message i intended:
*processor I**nferAvroSchema*:
- should retrieve types from analysing data from csv. property "Input
Content Type" lists CSV, JSON but in reality the property "Number Of
Records To Analyze" only
+1 (binding)
Verified signatures
Built and ran a dummy flow to ensure basic capabilities
Verified that NIFI-7076 and NIFI-7059 were both addressed.
Thanks for handling the RC Joe!
-Mark
> On Jan 31, 2020, at 3:11 PM, Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for
+1 (non-binding)
-Ran full clean install on OS X (Catalina 10.15.2)
-Tested secure NiFi with secure NiFi Registry (0.5.0)
-Ran basic flows successfully
-Reviewed core UI and documentation fixes/updates
Drew
> On Jan 31, 2020, at 3:11 PM, Joe Witt wrote:
>
> Hello,
>
> I am pleased to be
+1 (non-binding)
Verified signatures and hashes
Built and run on MacOS with Java 11 (OpenJDK Runtime Environment
Zulu11.33+15-CA (build 11.0.4+11-LTS))
Built and ran some simple flows
Verified some of the bugs fixed (NIFI-7032, NIFI-7069)
One minor thing that shouldn't hold the release IMO...
+1 (non-binding)
Verified checksums, signatures, and commit hash
Ran build and tests on OpenJDK 1.8.0_242 on Linux
Ran rpm build target and tested install
Created small cluster and ran some flows
Note: I ran into intermittent TestListFile failures on OS X (there are existing
JIRAs for these)
One thing I should mention is that schema inference is simply not capable
of exploiting Avro's field aliasing. That's an incredibly powerful feature
that allows you to reconcile data sets without writing a single line of
code. For example, I wrote a schema last year that uses aliases to
reconcile
**1. processor ValidateRecord*[1.1] *OK* - allows *getting schema
automatically via header line* and*mandatorysubset of fields* (presence)
via the 3 schema properties --> suggest renameproperties to make clear
those at processor level are "mandatory check" vsthe schema on reader which
is the well
+1 binding
Verified sigs, hashes, etc per the typical release helper process.
Since the list of resolved issues were so small I verified most, with the
exception of 7051, 7080, and 7069. All others appear to be resolved.
Only built on PopOS and Centos due to superbowl -- but everything
+1 (non-binding)
- [x] Non-RPM (usual) build with Java 8.
- [x] Deploy on 3 node secured cluster in CentOS 7.7.0 and run on Java 8.
- [x] Non-RPM (usual) build with Java 11.
- [x] Deploy on 1 node non secured cluster in CentOS 7.7.0 and run on Java 11.
Thanks for working for the release!
On
18 matches
Mail list logo
