Apache NiFi Community,
I am pleased to announce that the 0.13.0 release of Apache NiFi MiNiFi C++
passes with
3 +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.org/thre
Hi all,
This may be too basic/self-explanatory to count as a goal at all, but will
site-to-site interoperability between NiFi 1.x and NiFi 2.x nodes will be
preserved?
Regards,
Isha
-Oorspronkelijk bericht-
Van: David Handermann
Verzonden: zondag 11 december 2022 04:08
Aan: Otto Fow
Hi Isha,
As the scope of the proposed release goals does not include changing the
Site-to-Site protocol, that setup should work. Any kind of breaking
compatibility changes will need to be documented, but the general goal is
to make the upgrade as seamless as possible to encourage adoption.
Regard
Team,
Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
recent discussion thread [2], I am calling this vote to adopt the following
as Release Goals for NiFi 2.0:
1. Remove Java 8 support and require Java 11
2. Remove deprecated components
3. Remove deprecated component pr
+1 binding
On Mon, Dec 12, 2022 at 10:02 AM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
+1 (non-binding)
Cheers,
---
Chris Sampson
IT Consultant
chris.samp...@naimuri.com
> On 12 Dec 2022, at 17:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt t
+1 (binding)
On Mon, Dec 12, 2022 at 12:27 PM Chris Sampson
wrote:
>
> +1 (non-binding)
>
>
> Cheers,
>
> ---
> Chris Sampson
> IT Consultant
> chris.samp...@naimuri.com
>
>
> > On 12 Dec 2022, at 17:02, David Handermann
> > wrote:
> >
> > Team,
> >
> > Following positive feedback on NiFi 2.0 P
+1 (binding)
> On Dec 12, 2022, at 12:02 PM, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8 su
+1 (binding)
On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
+1 (non-binding)
On Mon, Dec 12, 2022, 6:42 PM Matt Gilman wrote:
> +1 (binding)
>
> On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> > recent discussion threa
+1 (binding)
On Dec 12, 2022 at 12:41:16, Matt Gilman wrote:
> +1 (binding)
>
> On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> Team,
>
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
>
> recent discussion thread [2], I
+1 (binding)
On Mon, Dec 12, 2022 at 12:02 PM David Handermann
wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8 support
Hello all,
I hope this is the right thread to raise this.
I have recently been working with nipyapi[1] creating flows and found
challenge when configuring components(processors/CS) properties whose
PropertyDescriptor$displayName is different than PropertyDescriptor$name.
I had to use browser inspe
+1 (non-binding)
> On 2022. Dec 12., at 18:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8
+1 (non-binding)
David Handermann schrieb am Mo., 12. Dez.
2022, 18:02:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8 suppor
Hello,
The purpose of displayName is to allow changing the name shown in the
UI without breaking existing flows, meaning it still uses the original
name behind the scenes in flow xml/json, but just shows a different
name in the UI, so the primary purpose is for them to be different.
Since it was
+1 (binding)
> On Dec 12, 2022, at 12:02 PM, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8 su
+1 (non-binding)
> On Dec 12, 2022, at 6:02 PM, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8
+1 (non-binding)
> On 2022. Dec 12., at 18:02, David Handermann
> wrote:
>
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8
19 matches
Mail list logo
