details.
Please provide your thoughts on the general process, and highlight
particular areas of concern.
Regards,
David Handermann
[1] https://github.com/eclipse/jetty.project/issues/7958
[2]
https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6
[3] https
Thanks Kevin, +1 for preparing a release of the NAR Maven plugin.
Regards,
David Handermann
On Wed, Jun 15, 2022 at 11:58 AM Joe Witt wrote:
> +1
>
> On Wed, Jun 15, 2022 at 9:41 AM Kevin Doran wrote:
>
> > All,
> >
> > If there are no objections, I would like to
+1 (binding)
- Verified signature and hashes
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-332
- Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.3
Thanks Kevin!
Regards,
David Handermann
On Thu, Jun 16, 2022 at 4:11 PM Kevin Doran wrote:
> Hello Apache NiFi Community,
>
configuration ShellUserGroupProvider
- Ran NiFi Registry on Azul Zulu JDK 1.8.0-322
- Created Buckets
- Ran NiFi Encrypt Config Toolkit with AES-GCM
Thanks Joe!
Regards,
David Handermann
On Mon, Jun 13, 2022 at 11:39 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling
a more definite
implementation plan following the release of NiFi 1.17.0.
Regards,
David Handermann
On Wed, Jun 15, 2022 at 12:31 PM Kevin Doran wrote:
> Pierre and David, I agree with this project goals:
>
>
>- a 2.x release that drops support for Java 8 (requires at least
notifications
- NIFI-10036 Verified PutElasticsearchRecord with Elasticsearch 7.17.3
Thanks Joe!
Regards,
David Handermann
On Sun, May 22, 2022 at 10:44 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.16.2.
>
&
its own set of configuration
options depending on how it is deployed, but understanding the file-based
approach in the StandardSSLContextService should provide a helpful
background.
Regards,
David Handermann
[1]
https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-standard-services/nifi
+1 (binding)
- Verified signatures and hashes
- Ran build of nifi-nar-maven-plugin on Ubuntu Linux 22.04 with Azul Zulu
JDK 1.8.0-332
- Ran build of NiFi using nifi-nar-maven-plugin 1.3.5
- Verified updates to nifi-runtime-manifests.json
Thanks Bryan!
Regards,
David Handermann
On Wed, Jul 20
libraries present in root library directory
Thanks Joe!
Regards,
David Handermann
On Thu, Jul 28, 2022 at 9:28 AM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.17.0.
>
> The source zip, including signatures, digests,
of the year. We can discuss the
particulars in a separate thread.
Regards,
David Handermann
[1] https://issues.apache.org/jira/projects/NIFI/versions/12351438
[2] https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34
On Sat, Jul 23, 2022 at 8:18 AM Joe Witt wrote:
> Mike
>
> Needs
directory
I submitted the following pull requests to address the issues:
- NIFI-10284 https://github.com/apache/nifi/pull/6250
- NIFI-10286 https://github.com/apache/nifi/pull/6251
Regards,
David Handermann
On Mon, Jul 25, 2022 at 9:57 PM Joe Witt wrote:
> Hello,
>
> I a
Processor Property in EvaluateXPath and
EvaluateXQuery mitigates the vulnerability for those Processors. No mitigation
is available for the ValidateXml Processor or the Standard Content Viewer.
Credit:
David Handermann at exceptionfactory.com reported this issue.
References:
https
Mike,
Following up on this thread, I created the following Jira issue and pull
request to address the problem for future builds on Java 17:
https://issues.apache.org/jira/browse/NIFI-9968
https://github.com/apache/nifi/pull/6000
Regards,
David Handermann
On Mon, Apr 25, 2022 at 4:32 PM David
-providers.xml
https://issues.apache.org/jira/browse/NIFI-9980 - Corrected Google
dependencies for GCP components
Regards,
David Handermann
On Mon, May 9, 2022 at 11:39 AM Joe Witt wrote:
> Team,
>
> Just saw this one land https://issues.apache.org/jira/browse/NIFI-9993.
&g
Apache NiFi Community,
On behalf of the Apache NiFi Project Management Committee, I am very
pleased to announce that Nathan Gough has accepted the invitation to join
the PMC.
Nathan has been a consistent contributor to the project since 2018. In
addition to developing features and fixes, he
at should provide a good baseline for a subsequent PR to
implement a new hashing strategy.
Regards,
David Handermann
On Tue, Oct 25, 2022 at 1:36 PM Mike Thomsen wrote:
> As-is, the deduplication-by-hash functionality appears to now be
> broken w/ Mongo 5 and higher. We can address tha
documentation in PutSFTP
Thanks Joe!
Regards,
David Handermann
On Thu, Sep 29, 2022 at 2:22 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.18.0.
>
> The source zip, including signatures, digests, etc. can be
,
David Handermann
On Thu, Sep 29, 2022 at 4:21 PM Dan S wrote:
> Sorry about that. I did not realize I could not include an image. Here is a
> text version:
>
> Warning:(624, 10) Dependency is duplicated in file(s):
> nifi-zendesk-processors
> Warning:(629, 10) Dependency is du
Dan,
Thanks for asking about these dependencies. The attached image did not come
through to the list, but the XML snippet shows the standard test
dependencies. These dependencies are applied to all modules by design, to
avoid unnecessary repetition in child modules.
Regards,
David Handermann
Dan,
The initial removal of duplicate dependencies sounds good on its own.
Enforcing the rules might take a bit more evaluation, so having it as a
separate issue seems like the best way forward.
Regards,
David Handermann
On Thu, Sep 29, 2022 at 5:11 PM Dan S wrote:
> Should the ticket incl
Mike,
Thanks for the link. Given that the Neo4j configuration is limited to
configuring trusted certificates from File sources, it looks like making
that a component property is the best approach.
Regards,
David Handermann
On Wed, Oct 12, 2022 at 6:38 AM Mike Thomsen wrote:
> Her
of sensitive properties
- Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 11.0.12 AMD64
- Created Buckets
- Verified Flow Version Control
- Ran NiFi Stateless on macOS 12.6 with Azul Zulu JDK 11.0.16 x86_64
Thanks Joe!
Regards,
David Handermann
On Mon, Oct 3, 2022 at 3:45 PM Joe Witt
cover
additional bases. Either way, having sufficient unit tests and
documentation would be helpful depending on the implementation approach.
Regards,
David Handermann
On Fri, Oct 7, 2022 at 10:06 AM Pierre Villard
wrote:
> Hi Dan,
>
> I personally think this is a fair addition to the e
/databind/ObjectMapper.java#L81
Regards,
David Handermann
On Fri, Oct 7, 2022 at 11:05 AM Dan S wrote:
> Mike,
> I noticed you did similar work in NIFI-5271
> <https://issues.apache.org/jira/browse/NIFI-5271>. Joe Witt commented
> there
>
> > We dont have guaranteed thre
.
Regards,
David Handermann
On Tue, Oct 11, 2022 at 12:36 PM Mike Thomsen
wrote:
> Neo4J for some reason doesn't support the standard Java keystore types
> or P12 files for its client SSL configuration. It requires the use of
> PEM files. Would it be better to extend the SSLContext serv
.
I appreciate the concern about potential disruption, and concern about
stability. These concerns are important to keep in mind as we move forward.
As long as we follow this approach, we should be able to maintain the level
of stability that the community rightly expects.
Regards,
David Handermann
traction on the 2.0 release goals
before attempting to sketch out a potential timeline.
Regards,
David Handermann
On Mon, Jan 9, 2023 at 3:50 PM Adam Taft wrote:
> Joe / team,
>
> Question on this. I think it would be helpful to understand the desired
> timelines for the first 2.0.
. These
improvements address several of the theoretical gaps between PostHTTP and
InvokeHTTP sending to ListenHTTP.
Nothing in the scope of NiFi 2.0 includes directly breaking support for
older processors, so running older components is a last resort option.
Regards,
David Handermann
On Wed, Jan 11
for future releases.
Regards,
David Handermann
On Wed, Nov 30, 2022 at 7:36 AM Mark Bean wrote:
> Sounds great Kevin. Thanks!
>
> Can you give a little more detail on the dependency duplication detection?
> How does it work? Does it detect different versions of the same dependency?
>
in a subsequent version 1 release.
Regards,
David Handermann
On Wed, Dec 7, 2022 at 1:50 PM ski n wrote:
> I read the proposal and seems like a very clear plan. The only thing I
> noticed:
>
> "Spring 6 <https://spring.io/blog/2022/11/16/spring-framework-6-0-goes-ga>
>
One point of clarification, the following sentence should read Java 17 as a
consideration for the minimum in a subsequent major release:
> It is probably necessary to consider *Java 17* support in a future
version, but Java 11 provides more of a transitional timeline.
Regards,
David Handerm
.
Regards,
David Handermann
On Mon, Dec 12, 2022 at 4:12 AM Isha Lamboo
wrote:
> 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,
>
> I
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
to Planned Release Goals. Please weigh
the general goals highlighted, and if there are no major roadblocks
identified, I will follow up soon with a vote thread.
Regards,
David Handermann
[1] https://lists.apache.org/thread/yj8scrdbx3pdo7990123mc03q24rn1m7
[2] https://lists.apache.org/thread
Apache NiFi Community,
I am pleased to announce that the vote to adopt NiFi 2.0 Proposed Release
Goals passes:
[13] +1 binding votes
[11] +1 non-binding votes
[0] 0 votes
[0] -1 binding votes
[1] -1 non-binding vote
This vote signifies approval of the following actions:
1. Rename NiFi 2.0
be opportunity for some refactoring.
Regards,
David Handermann
On Wed, Dec 14, 2022 at 3:27 PM Zoltán Kornél Török
wrote:
> +1 (non-binding)
>
> Nathan Gough ezt írta (időpont: 2022. dec. 14., Sze,
> 20:46):
>
> > +1 (binding)
> >
> > The proposal sounds great to me
> &
Thanks Joe!
Regards,
David Handermann
On Mon, Dec 5, 2022 at 1:58 PM Joe Witt wrote:
> Hello,
>
> Please note this is intended as a shorter than normal release cycle
> given the limited scope and the importance of getting some of these
> fixes to those already trying 1.
gt; have a
> >
> > > > formal
> >
> > > > > > vote on this proposal.
> >
> > > > > >
> >
> > > > > > Thanks,
> >
> > > > > > Pierre
> >
> > > > > >
>
to scoping for
version 1 releases.
Regards,
David Handermann
On Sat, Dec 10, 2022 at 8:42 PM Otto Fowler wrote:
> Sorry to be late to this, the goals seem great. The question that comes to
> my mind is will the current 1.x line will be maintained?
>
> That may be a parallel issue
Kevin,
Thanks for volunteering to handle the release process, please proceed.
Regards,
David Handermann
On Tue, Nov 29, 2022 at 3:19 PM Joe Witt wrote:
> +1 thanks Kevin
>
> On Tue, Nov 29, 2022 at 2:18 PM Kevin Doran wrote:
> >
> > Hi all,
> >
> > There’
Processors
Thanks Joe!
Regards,
David Handermann
On Wed, Nov 23, 2022 at 9:58 AM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.19.0.
>
> The source zip, including signatures, digests, etc. can be
Joe,
One additional note for 1.19.1, the following Jira issue and associated
pull request just merged resolve a regression in Kafka component
configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL
Mechanism:
https://issues.apache.org/jira/browse/NIFI-10919
Regards,
David Handermann
.509 Client Certificates is another
option for programmatic access, but there is no direct replacement for
One-Time Password Authentication.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-8931
On Mon, Jan 23, 2023 at 3:37 AM Daniel Chaffelson
wrote:
> Hi folks,
>
to make a plain HTTP connection to the NiFi HTTPS service.
Updating the request URL to start with https should resolve that particular
problem.
Regards,
David Handermann
[1] https://infra.apache.org/jira-guidelines.html#account
On Mon, Jan 30, 2023 at 8:26 AM Dorin Jacota
wrote:
> Hello team,
.
Regards,
David Handermann
On Fri, Jan 27, 2023 at 10:00 AM Yves Lamézec wrote:
> Hi NiFi development team,
>
> I'm encountering the issue described in
> https://issues.apache.org/jira/browse/NIFI-9989.
> I would like to know if there's an ETA for a fix and in which release it
>
with 1.19.0.
Regards,
David Handermann
On Thu, Nov 10, 2022 at 1:44 PM Joe Witt wrote:
> Team,
>
> We keep getting a slew of emails on various lists, slack, and the security
> list about commons text. We need a 1.18.1 or a 1.19.0.
>
> Given all that has already happened on 1.19.0 I'm in
Concurring with Matt, this sounds like a potential opportunity for a
scripted Processor implementation specific to Kotlin.
Regards,
David Handermann
On Mon, Nov 7, 2022 at 1:11 PM Matt Burgess wrote:
> Mike,
>
> As an alternative it might be worth looking into a processor
>
+1 binding
- Verified hashes and signatures
- Ran build using Maven 3.9.0
- Ran build on macOS 13.2.1 with Azul Zulu JDK 1.8.0-345 x86_64
- Ran NiFi main branch build using NAR Plugin 1.5.0
- Ran build of standalone NAR project using NAR Plugin 1.5.0
Thanks Kevin!
Regards,
David Handermann
to
redirect back to NiFi after concluding the logout process with Okta.
Regards,
David Handermann
On Mon, Apr 24, 2023 at 8:15 AM Nivetha Radhakrishnan Senthilkumar <
nivetha.radhakris...@inovalon.com> wrote:
> Hi Nifi Team,
>
> We are using okta to sign in our Nifi applicatio
a new approach.
I will comment on the pull request, and I think it works well as a targeted
change for Expression Language, then other issues can cover remaining
framework references.
Regards,
David Handermann
[1]
https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals
-1 binding
Thanks to macdoor615 testing 1.21.0-RC1 and reporting NIFI-11365 [1] I am
voting down the release candidate to correct OpenID Connect integration
with reverse proxy servers.
I have submitted a pull request [2] to correct the behavior.
Regards,
David Handermann
[1] https
Encryption Command does not truncate floating
point numbers
NIFI-11365 Verified OpenID Connect integration with reverse proxy and
context path changed
NIFI-11372 Verified Registry documentation is rendered as expected
Thanks Joe!
Regards,
David Handermann
On Mon, Apr 3, 2023 at 7:11 PM Joe Witt
!
Regards,
David Handermann
On Mon, Feb 6, 2023 at 2:55 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.20.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org
Thanks for filing the Jira issue! I added a comment describing the root
cause for the change in behavior, and also suggested a way to restore the
additional details.
I would be glad to review a pull request with changes.
Regards,
David Handermann
On Thu, Feb 9, 2023 at 9:56 AM Dan S wrote
-dependencies
goal
Thanks Kevin!
Regards,
David Handermann
On Mon, Jan 30, 2023 at 5:19 PM Kevin Doran wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi NAR Maven Plugin 1.4.0.
>
> The source being voted upon, in
Thanks Mark and Joe!
I'm willing to handle the Release Manager responsibilities for this one,
thanks for creating the Jira issue.
The Spring Framework upgrade PR has been merged, so I think if we can wrap
up these few items, we should be ready to go soon.
Regards,
David Handermann
On Wed, Jul
.
Anything else worth highlighting?
Regards,
David Handermann
[1]
https://issues.apache.org/jira/issues/?jql=project+%3D+NIFI+AND+fixVersion+%3D+1.23.0
[2] https://issues.apache.org/jira/browse/NIFI-11814
[3] https://issues.apache.org/jira/browse/NIFI-11825
as the default strategy for status history, we should
build in the resilient approach as a prerequisite to enabling it in the
default configuration.
Regards,
David Handermann
On Wed, Jul 19, 2023 at 8:31 AM Simon Bence
wrote:
> Thanks for the quick feedback!
>
> Joe: your concerns are relevan
://github.com/apache/nifi/pull/7504
Once that is reviewed and merged, I plan to prepare a release candidate
build.
Regards,
David Handermann
On Wed, Jul 19, 2023 at 11:14 AM David Handermann <
exceptionfact...@apache.org> wrote:
> Thanks Mark and Joe!
>
> I'm willing to handle the
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.23.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1230
The source being voted upon and the convenience binaries can be
Mark,
Thanks for the testing and turning around a fix for this scenario. It is
definitely worth correcting this behavior. Cancelling this Release
Candidate, and will plan on preparing RC2 after reviewing and merging the
correction.
Regards,
David Handermann
On Thu, Jul 20, 2023 at 11:15 AM Mark
On Thu, Jul 20, 2023 at 11:44 AM David Handermann <
exceptionfact...@apache.org> wrote:
> Mark,
>
> Thanks for the testing and turning around a fix for this scenario. It is
> definitely worth correcting this behavior. Cancelling this Release
> Candidate, and will plan o
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.23.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1231
The source being voted upon and the convenience binaries can be
to bring in a script
engine library should provide a better solution for the future. This also
should not be a blocker for an initial NiFi 2.0, but it is worth
highlighting given the general interest in scripted components.
Regards,
David Handermann
On Thu, Jun 1, 2023, 11:38 PM Dirk Arends wrote
.
The system tests have had sporadic failures recently, so it seems best to
wrap up NIFI-11591 [1] before proceeding.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-11591
On Wed, May 24, 2023 at 11:39 AM Joe Witt wrote:
> Team,
>
>
> https://issues.apache.org
releases.
Thanks Joe!
Regards,
David Handermann
On Tue, Jun 6, 2023 at 4:38 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.22.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.23.0.
Please review the following guide for how to verify a release candidate
build:
https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
The source being voted
Apache NiFi Community,
I am pleased to announce that the 1.23.0 release of Apache NiFi passes:
8 +1 (binding) votes
6 +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:
The Apache NiFi team would like to announce the release of Apache NiFi
1.23.0.
Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute
data. Apache NiFi was made for dataflow. It supports highly configurable
directed graphs
of data routing, transformation, and
gt; -Verified Core UI and Documentation changes
>
> Drew
>
> > On Jul 25, 2023, at 5:32 PM, David Handermann <
> exceptionfact...@apache.org> wrote:
> >
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
&g
Thanks Mark,
The Jira issue provides helpful steps for reproducing the problem. There
seems to be an issue specific to Registry with the H2 upgrade from 2.1.214
to 2.2.220.
I am cancelling this release candidate so we can track this down.
Regards,
David Handermann
On Fri, Jul 21, 2023 at 12:31
Team,
For reference, the vote on RC2 is cancelled as noted in this thread:
https://lists.apache.org/thread/njkkd9v8mly53wb867gfgprybptr4xs8
Regards,
David Handermann
On Fri, Jul 21, 2023 at 12:31 PM Mark Bean wrote:
> -1 (non-binding)
>
> Discovered an H2 database migration issu
in a
selected number of dependency upgrades.
I am willing to handle the Release Manager responsibilities. If there is a
positive response to this approach, I can put together a selected list of
issues next week.
Regards,
David Handermann
[1]
https://issues.apache.org/jira/issues/?jql=project%20
backporting, but they do require careful attention.
Regards,
David Handermann
On Mon, Aug 7, 2023 at 4:04 PM Matt Burgess wrote:
> In my opinion that's ok, but I think it would be helpful if a PR is
> going to be backported to support/nifi-1.x that the PR author provides
> two PRs, on
advantage of new features on the main branch. We have already started doing
this in terms of certain libraries, and more work is in progress.
Regards,
David Handermann
On Mon, Aug 7, 2023 at 7:54 PM Mark Bean wrote:
> I was working on a very similar response. Thanks Joe for the cl
that matches the
__Secure-Request-Token cookie.
Regards,
David Handermann
[1] https://apachenifi.slack.com/archives/C0L9VCD47/p1690797006846169
[2]
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#csrf-protection
On Mon, Jul 31, 2023 at 7:09 AM Zhiyi Ni wrote:
> Hello, I have s
, which some
Processors support, so that seems like the general direction to go.
If you have additional findings, feel free to start a new developer list
thread and that may gather additional feedback.
Regards,
David Handermann
On Wed, Jun 21, 2023 at 12:17 AM Dirk Arends
wrote:
> Since initia
of scenarios.
Regards,
David Handermann
On Thu, Jun 22, 2023 at 9:09 AM Mike Thomsen wrote:
> A colleague found this "CVE" report for H2. I agree with the H2 devs that
> it's a big joke of a CVE, but it's something we might want to add something
> to the documentation to discu
scripting engines.
We should review the status of things after addressing some of the larger
outstanding deprecation removals.
Regards,
David Handermann
[1] https://github.com/apache/nifi/pull/7397
[2] https://issues.apache.org/jira/browse/NIFI-11717
[3]
https://cwiki.apache.org/confluence/display/NIFI
to HTTP operations of course, but there may be some overlapping
concerns.
This might be a case where publishing the Processors in a separate GitHub
repository would be a better next step. That would provide some opportunity
for community review and use.
Regards,
David Handermann
[1] https
to start
the build process soon after these are reviewed and merged.
Regards,
David Handermann
[1] https://issues.apache.org/jira/projects/NIFI/versions/12353541
On Mon, Aug 14, 2023 at 2:22 AM Peter Turcsanyi
wrote:
> +1, thanks David!
>
> On Mon, Aug 14, 2023 at 8:56 AM Krisztina Z
two years, so it may be worth considering
removal from the main branch as part of NiFi 2.0.
Regards,
David Handermann
On Mon, Jan 22, 2024 at 1:02 PM Gábor Gyimesi wrote:
>
> Hi,
>
> I've also found an issue with RC earlier today, that the Minifi C2 server
> is not working anymor
.
Regards,
David Handermann
On Mon, Jan 22, 2024 at 10:05 AM Chris Sampson
wrote:
>
> Maven might have got itself confused. Could you try clearing out your
> .m2/repository (at least if anything in the org/apache/nifi directories)?
>
> Note that if you delete the whole local repo,
Arpad,
Thanks for the reply.
I submitted a pull request [1] which deletes the modules from the main
branch. As described in the Jira issues, the purpose is to eliminate
maintenance of the C2 server components as they stand.
[1] https://github.com/apache/nifi/pull/8291
Regards,
David Handermann
Thanks for the confirmation, Arpad.
Pending the approval of the pull request, I will update the Migration
Guide and NiFi 2.0 Deprecated Components and Features pages.
Regards,
David Handermann
On Mon, Jan 22, 2024 at 4:53 PM Arpad Boda wrote:
>
> Thanks, David,
>
> At the moment
with a clean slate, as outlined in the reference Jira issue.
I have captured the proposal in NIFI-12657 [2] and I will be
submitting a pull request to implement the removal.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-9428
[2] https://issues.apache.org/jira/browse/NIFI-12657
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M2.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
The source being voted on and the
Hi Nissim,
Can you provide some additional details about the runtime environment?
Is NiFi Registry running in a container, or on a virtual machine? Some
application log snippets would also be helpful.
Regards,
David Handermann
On Wed, Jan 24, 2024 at 12:40 PM Nissim Shiman
wrote:
>
>
Cancelling NiFi 2.0.0-M2 RC2.
On Wed, Jan 24, 2024 at 2:32 PM David Handermann
wrote:
>
> Hi Nissim,
>
> Thanks again for flagging this issue.
>
> On closer evaluation, there is a problem with the NiFi Registry Data
> Source configuration, introduced on the main bra
the problem.
I am cancelling RC2 and will follow up with RC3 after this pull
request is merged.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-12666
On Wed, Jan 24, 2024 at 1:10 PM David Handermann
wrote:
>
> Hi Nissim,
>
> Can you provide some additional d
for newUsername, and a password
of at least 12 characters for newPassword.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-9500
On Sat, Dec 16, 2023 at 2:25 PM Amin Adatia wrote:
>
> Hi
>
> I have installed nifi-1.16.3 and I would like to find out how to create a
>
to evaluate a resilient storage solution instead of a
composite solution.
Regards,
David Handermann
On Mon, Dec 11, 2023, 6:23 AM Pierre Villard
wrote:
> Hi David and Bryan, thanks for the feedback.
>
> David,
>
> Regarding the source and destination. It was just an example. The
solution.
Regards,
David Handermann
On Fri, Dec 8, 2023 at 8:32 AM Pierre Villard
wrote:
>
> Team,
>
> I just published a feature proposal here:
> https://cwiki.apache.org/confluence/display/NIFI/State+Management+improvements+for+Disaster+Recovery+scenarios
>
> This feature p
, with the goal of pushing the new version to production early
next week.
Regards,
David Handermann
[1] https://github.com/james-elliott
[2] https://github.com/apache/nifi-site/tree/main-staging
responsibilities for a NiFi 2.0.0-M2 version, ideally at some
point this week.
Regards,
David Handermann
[1] https://issues.apache.org/jira/projects/NIFI/versions/12353861
[2] https://github.com/apache/nifi/pull/8248
[3] https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals
issue.
Regards,
David Handermann
On Tue, Jan 16, 2024 at 3:01 PM Lucas Ottersbach
wrote:
>
> Hey team,
>
> looking forward to the upcoming releases.
>
> Is there a chance we can land PR#8244 [1] / NIFI-12595 [2] or a variant
> thereof in the next 1.x release?
> I
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M1.
Version 2.0.0-M1 is the initial milestone release version of Apache NiFi 2.0.0.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute
data.
https://nifi.apache.org
The release
+1 binding
On Wed, Nov 22, 2023 at 8:48 PM David Handermann
wrote:
>
> Team,
>
> Thank you for your patience and continued support in reviewing these
> release candidates.
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 2.0.0-M1.
>
&g
Apache NiFi Community,
I am pleased to announce that the 2.0.0-M1 release of Apache NiFi passes:
4 +1 (binding) votes
6 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
Here is the vote thread:
Verified LICENSE and NOTICE included in nifi-standard-shared-nar
- NIFI-12377 Verified Jython Script Engine marked as deprecated
- NIFI-12392 Verified Additional Details linked in component documentation
Thanks Pierre!
Regards,
David Handermann
On Thu, Nov 23, 2023 at 9:15 AM Pierre Villard
101 - 200 of 270 matches
Mail list logo
