+1 (binding)
On Tue, Aug 15, 2023 at 1:06 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.1.
>
> Please review the following guide for how to verify a release candid
Apache NiFi Community,
I am pleased to announce that the 1.23.1 release of Apache NiFi passes:
5 +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:
https://lists.apache.org/thread/wvlg8b
The Apache NiFi team is pleased to announce the release of Apache NiFi 1.23.1.
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 syst
serious enough that we should release a new patch
version 1.23.2, limited to this particular fix.
I plan to prepare a release candidate build and send out a
short-duration vote thread later today.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-11971
[2] https
Thanks everyone for the quick replies!
I am starting the release candidate build process and will send a
separate email when the vote is ready.
Regards,
David Handermann
On Mon, Aug 21, 2023 at 10:30 AM Nándor Soma Abonyi
wrote:
>
> +1
>
> > On 2023. Aug 21., at 15:58, D
Team,
NOTE: This is a shortened vote window given the narrow scope of changes.
I am pleased to be calling this vote for the source release of Apache
NiFi 1.23.2.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/display/NIFI/How+t
+1 (binding)
On Mon, Aug 21, 2023 at 3:16 PM David Handermann
wrote:
>
> Team,
>
> NOTE: This is a shortened vote window given the narrow scope of changes.
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.23.2.
>
> Please review the
Apache NiFi Community,
I am pleased to announce that the 1.23.2 release of Apache NiFi passes:
8 +1 (binding) votes
1 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
Here is the vote thread:
https://lists.apache.org/thread/o17t1q
The Apache NiFi Team is pleased to announce the release of Apache NiFi 1.23.2.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
https://nifi.apache.org/download.
Java security
policy is highly recommended.
Regards,
David Handermann
On Wed, Aug 23, 2023 at 10:34 AM Martin Fong wrote:
>
> We have an MS SQL connection that worked fine with RH7.
>
> Once we upgraded to RH9 and the crypto policies=DEFAULT
> (https://access.redhat.com/docu
+1
On Thu, Aug 24, 2023 at 10:14 AM Marton Szasz wrote:
>
> +1. I'm not aware of any blockers. Thanks for taking on RM duties.
>
> On Thu, Aug 24, 2023 at 5:04 PM Joe Witt wrote:
> >
> > +1 a lot of nice things in there!
> >
> > On Thu, Aug 24, 2023 at 7:52 AM Martin Zink wrote:
> >
> > > Hi co
initial implementation, but it is something I am
planning to evaluate as time allows.
For now, something focused narrowly on FlowFile Version 3 encoding
seems like the best approach.
I recommend referencing this discussion in a new Jira issue and
outlining the general design goals.
Regards,
David
oject focused on core capabilities.
Thoughts?
Regards,
David Handermann
[1] https://cert-manager.io
[2] https://github.com/FiloSottile/mkcert
[3]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22TLS%20Toolkit%22
ly on
physical hardware. With the need to support various approaches,
however, some type of configuration encryption remains a relevant
concern.
Regards,
David Handermann
On Wed, Sep 13, 2023 at 10:19 AM Isha Lamboo
wrote:
>
> Hi David,
>
> My primary use for the TLS toolkit is for lab de
to provide a
bridge while we scope out a rewritten version.
Regards,
David Handermann
On Wed, Sep 13, 2023 at 3:24 PM Joe Witt wrote:
>
> David
>
> Fully supportive.
>
> I'll take it a step further and indicate that I am now an advocate of
> removing anything we ha
forward with an M1 release version.
Regards,
David Handermann
On Tue, Sep 26, 2023, 12:58 PM Joe Witt wrote:
> The Packager thing looks pretty close to being ready anyway. I dont see
> that holding anything up on any line at this point.
>
> I don't have any heartburn waiting fo
will be some additional work to support migration
on version 1 support branch.
If we want to move forward with a 1.24 release within a week or so,
then these changes could be targeted for 1.25. If we want to wait a
few weeks, then I could see this being incorporated in 1.24.
Regards,
David
Joe,
Thanks for the reply, that sounds good.
For reference, here is the Jira issue for tracking the initial implementation:
https://issues.apache.org/jira/browse/NIFI-12206
Regards,
David Handermann
On Tue, Oct 10, 2023 at 6:53 PM Joe Witt wrote:
>
> David
>
> I think we can ho
migrate to the latest version 1 release, and
then upgrade to version 2.
Regards,
David Handermann
On Thu, Oct 12, 2023 at 12:24 PM Mike Thomsen wrote:
>
> When H2 goes, what will the upgrade path look like?
>
> On Tue, Oct 10, 2023 at 7:57 PM David Handermann <
> exception
Mike,
Yes that's correct, here's the Jira issue for tracking the migration work:
https://issues.apache.org/jira/browse/NIFI-12219
Regards,
David Handermann
On Thu, Oct 12, 2023, 5:29 PM Mike Thomsen wrote:
> This Xodus?
>
> https://github.com/JetBrains/xodus
>
>
1.24.0
incorporating additional upgrades, features, and deprecation warnings.
Regards,
David Handermann
On Thu, Oct 12, 2023 at 9:44 PM David Handermann
wrote:
>
> Mike,
>
> Yes that's correct, here's the Jira issue for tracking the migration work:
>
> https://issues
multiple versions, I would
be glad to handle release manager duties for one of the versions.
Regards,
David Handermann
[1] https://issues.apache.org/jira/projects/NIFI/versions/12339599
[2] https://issues.apache.org/jira/projects/NIFI/versions/12353443
.
Regards,
David Handermann
On Wed, Nov 8, 2023 at 5:53 PM Mark Payne wrote:
>
> Hey Pierre,
>
> I ran into a couple of issues (they appear to be timing issues) around the
> Python stuff on startup. I think we need to hold off on the release until
> these are resolved but I thi
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M1.
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 the and the conveni
Otto,
Can you provide the exact command you are running? Running the
following command from the NiFi home directory should work on a new
installation:
grep Generated logs/nifi-app.log
Regards,
David Handermann
On Tue, Nov 14, 2023 at 7:57 AM Otto Fowler wrote:
>
> I”m trying to veri
[2] https://github.com/apache/nifi/commits/support/nifi-1.x
Regards,
David Handermann
On Tue, Nov 14, 2023 at 11:02 AM Pierre Villard
wrote:
>
> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.24.0.
>
> Please review the following gu
,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-12373
On Wed, Nov 15, 2023 at 6:33 AM Csaba Bejan wrote:
>
> +1 (binding)
>
> - Went through the helper guide and did a clean build
> - Verified signatures and hashes
> - Built on OSX 13.5.2
> - Java version: Z
changes included version
updates, which is another reason for including the issue in the
release version.
Regards,
David Handermann
On Wed, Nov 15, 2023 at 2:11 PM Dan S wrote:
>
> David,
> I would like to note one thing regarding the release notes. The following
> ticket
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M1.
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 the and the conveni
Marton,
Thanks for catching that mismatch. The problem was due to a conflict
with the previous copy of the source-release.zip in Subversion.
I am cancelling this release candidate and will send out a new thread
to avoid any confusion.
Regards,
David Handermann
On Fri, Nov 17, 2023 at 5:01 PM
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M1.
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 the and the conveni
!
Regards,
David Handermann
On Thu, Nov 16, 2023 at 1:01 PM Pierre Villard
wrote:
>
> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.24.0.
>
> Please review the following guide for how to verify a release candidate
> build:
>
introduces additional unit tests for the NarUnpacker, which
was the source of the problem as a result of recent changes for
NIFI-12294 [3].
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-12392
[2] https://github.com/apache/nifi/pull/8052
[3] https://issues.apache.org/jira/browse
Team,
I am cancelling RC3 for 2.0.0-M1 based on the additional details
documentation issue NIFI-12392 [1]. I will start another release
candidate build once the correction is merged.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-12392
On Sat, Nov 18, 2023 at 2:17 PM
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M1.
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 the and the conveni
] to include the python3-venv package.
Although it might be considered a build issue that could be resolved
for release, it is early enough in the vote that I am cancelling this
release candidate and will publish another after the resolution is
merged.
Regards,
David Handermann
[1] https
Team,
I am cancelling RC4 based on this finding.
Regards,
David Handermann
On Tue, Nov 21, 2023 at 9:25 AM David Handermann
wrote:
>
> Gabor,
>
> Thanks for finding and highlighting this problem. I confirmed the same
> issue and the resolution you noted. The Dockerfile for
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.0.0-M1.
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 the and the conveni
marked as deprecated
- NIFI-12392 Verified Additional Details linked in component documentation
Thanks Pierre!
Regards,
David Handermann
On Mon, Nov 20, 2023 at 1:13 PM Pierre Villard
wrote:
>
> Team,
>
> I am pleased to be calling this vote for the source release of Apache N
support H2, but
version 2.0.0 will require upgrading to 1.24.0 before upgrading to
2.0.0.
Regards,
David Handermann
On Wed, Nov 22, 2023 at 12:03 PM Nissim Shiman
wrote:
>
> Team,
>
>
> I'm having difficulty migrating from registry 1.22.0 or earlier to 2.0.0-M1.
> Th
-12403 [1]. The rest of the release will remain
unchanged, which should make it easier to vote on the next version.
Thanks again for your work and patience as we move toward the next
release!
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-12403
On Wed, Nov 22, 2023 at 12
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.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/
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
+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:
https://lists.apache.org/thread/3pr0h
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 artif
processing, dropping
the group membership as you described.
I created NIFI-12418 [2] to track the issue. Resolving the problem
looks like it will require some internal adjustments to the refresh
handling process that generates the updated application bearer token.
Regards,
David Handermann
[1
a case-by-case basis, but as
we continue to make progress on a full 2.0.0 release, this approach
will allow Release Managers to maintain the standard use of the Fix
Version field as the definitive marker for issues resolved in a
particular version.
Regards,
David Handermann
[1] https
, named something like Target Version.
However, with improvements and new features primarily targeting the
main branch, I'm not sure that will be necessary in the long run.
Regards,
David Handermann
On Wed, Nov 29, 2023 at 10:09 AM Dan S wrote:
>
> David,
> What about tickets only
posed 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 featur
er 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. T
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
>
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 apprec
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 convenience
RC1 for 2.0.0-M2 is cancelled.
On Mon, Jan 22, 2024 at 9:23 AM David Handermann
wrote:
>
> Joe,
>
> Thanks for highlighting the build issue related to the optional
> profile for the new UI. In the interest of maintaining consistency in
> the source release, I agree this issue
-51074. Although this does not appear to
have a direct impact on NiFi usage, it would be helpful to include as
well.
I am cancelling RC1 and I will follow up with an RC2 build after
getting the json-path 2.9.0 upgrade reviewed and merged.
Regards,
David Handermann
On Mon, Jan 22, 2024 at 9:15 AM Joe
steps, it should not
try to retrieve release versions at all. Can you provide the command
you used for the initial build?
Regards,
David Handermann
On Mon, Jan 22, 2024 at 9:52 AM Dan S wrote:
>
> Sorry typo in my previous email
> would like to bring to your attention that I had a problem
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 a
.
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, then
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
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
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 convenience
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:
>
>
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
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 branch a
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 convenience
Chris,
Thanks for finding this problem.
I created a Jira issue NIFI-12676 [1] for tracking and submitted a
pull request to correct the problem.
I am cancelling RC3 and will proceed with a new build after this pull
request is merged.
Regards,
David Handermann
[1] https://issues.apache.org/jira
Cancelling RC3.
On Thu, Jan 25, 2024 at 4:16 PM David Handermann
wrote:
>
> Chris,
>
> Thanks for finding this problem.
>
> I created a Jira issue NIFI-12676 [1] for tracking and submitted a
> pull request to correct the problem.
>
> I am cancelling RC3 and will pro
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 convenience
Framework or requiring new
releases at that level. Although this would require a separate
installation process for Python-based components, this could follow an
approach similar to what is already required for optional Java-based
components.
Thanks in advance for your consideration.
Regards,
David
the category of convenience builds. Initially, I think
the NiFi framework release would not include the Python extension
components. However, having a few short steps on installation, linked
from the download page, seems like it would provide a way forward.
Regards,
David Handermann
On Fri, Jan 26
Hi Gabor,
The Docker Hub release process is independent of the source release
process, and is technically considered a convenience binary build.
>From that perspective, I don't think it is a concern for this release
vote of 1.25.0, but worth noting.
Regards,
David Handermann
On Fri
.
Based on the fact that the system tests are not part of the standard
review, and the fact that the failure relates to the test code itself,
I do not see this as a blocking issue for releasing this version.
Thanks Pierre!
Regards,
David Handermann
On Thu, Jan 25, 2024 at 12:53 PM Pierre Villard
+1 binding
On Thu, Jan 25, 2024, 8:29 PM David Handermann
wrote:
> 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
Apache NiFi Community,
I am pleased to announce that the 2.0.0-M2 release of Apache NiFi passes:
6 +1 (binding) votes
6 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
The release artifacts will be published in the next 24 hours.
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M2.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
https://nifi.apache.org/downloa
Python
APIs, but the Python Extensions repository would have its own
decoupled set of tests.
Regards,
David Handermann
On Thu, Feb 1, 2024 at 11:05 AM Gábor Gyimesi wrote:
>
> Hi David,
>
> Currently we are in the process of implementing support for the NiFi python
> process
Marton,
Thanks for raising the question and implementing the solution!
Regards,
David Handermann
On Thu, Feb 22, 2024 at 12:14 PM Marton Szasz wrote:
>
> Hi Joe, and anyone interested,
>
> I initially didn't look at the code, just wanted to confirm that it
> wasn't a
ems like the more significant problem. For this reason, it
seems better to rely on external operations to produce Avro schema
definitions, rather than supporting that in NiFi itself.
Those are my initial thoughts, perhaps others can provide additional
perspective.
Regards,
David Handermann
On Sat,
more? How would someone prepare a JAR for referencing in this
proposed registry?
Regards,
David Handermann
On Thu, Mar 7, 2024 at 4:30 PM Mike Thomsen wrote:
>
> You raise some good points, but I think there's still ample room for
> file-based schema registries within NiFi. With reg
main branch. That will provide a
clean slate for new Service and Processor implementations, without
concern for uncertain compatibility questions.
Regards,
David Handermann
On Mon, Mar 18, 2024 at 2:35 PM Matt Burgess wrote:
>
> What do y'all think about removing the individual connection p
components. That should put things in a good place to land the new
capabilities when they are ready. It also resolves the current
vulnerability findings with the legacy driver, so this approach is
helpful on several fronts.
Regards,
David Handermann
On Mon, Mar 18, 2024 at 3:30 PM Matt Burgess wrote
.
I have not taken a close look at the Matt's branch, and the details of
the abstraction are important, but having the abstraction can be
useful to avoid getting back to this same situation.
Regards,
David Handermann
[1] https://github.com/apache/cassandra-java-driver/
On Tue, Mar 19, 2024
. That is
the kind of abstraction that would be ideal, and I believe that also
aligns with what Matt has described.
Regards,
David Handermann
On Tue, Mar 19, 2024 at 1:45 PM Mike Thomsen wrote:
>
> ** we can dump v3 **DRIVER** compatibility, since later 4.X Java drivers
> are backward c
API level.
Regards,
David Handermann
On Wed, Mar 20, 2024 at 8:25 AM Mike Thomsen wrote:
>
> Matt/David,
>
> I got some time this morning to take a crack at directly migrating it over
> to the DataStax 4.17 driver. Definitely got a lot of work to do, but so far
> I haven&#x
er of
abstraction at the Controller Service API level.
Regards,
David Handermann
On Fri, Mar 22, 2024 at 8:13 AM Mike Thomsen wrote:
>
> Work so far: https://github.com/MikeThomsen/nifi/tree/cql-changes
>
> On Thu, Mar 21, 2024 at 9:52 AM Mike Thomsen wrote:
>
> > Matt/David,
> &g
hours.
Here is the vote thread:
https://lists.apache.org/thread/zyzddty6dtv0jcxxjqb8p13ls6gfhc2l
Regards,
David Handermann
The Apache NiFi Team is pleased to announce the release of Apache NiFi
API 2.0.0.
This is the first release of the Apache NiFi API as a standalone module.
The Apache NiFi API provides the public contract for integrating
internal and external extension components. Apache NiFi API 2.0.0
provides th
plan to prepare the release and call for a vote
soon.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-13773
f1
> > > > Java version: 21.0.3, vendor: Red Hat, Inc., runtime:
> > > > /usr/lib/jvm/java-21-openjdk-21.0.3.0.9-1.el8.x86_64
> > > > Default locale: en_US, platform encoding: UTF-8
> > > > OS name: "linux", version: "4.18.0-51
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi NAR Maven Plugin 2.1.0.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification+for+NiFi+NAR+Maven+Plugin
The s
Thanks Lucas!
I updated the Confluence pages with the correct link to the PGP Keys.
Regards,
David Handermann
On Thu, Sep 19, 2024 at 3:56 PM Lucas Ottersbach
wrote:
>
> Ran through the RC verification guide.
> +1 (non-binding)
>
> A side node: I noticed that the PGP keys are no
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi API 2.0.0.
This is the first release of nifi-api as a separate module, following
the recent vote in favor:
https://lists.apache.org/thread/p6d7qsyto8x8xqzr6scp3fp33lrbb82c
Please review the following guide for how
The Apache NiFi Team is pleased to announce the release of Apache NiFi
NAR Maven Plugin 2.1.0.
The Apache NiFi NAR Maven Plugin supports building NiFi Archives using
Apache Maven for deployment to runtime systems.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distrib
ional dependency loading concepts for Python.
Regards,
David Handermann
On Tue, Sep 24, 2024 at 9:41 AM Joe Witt wrote:
>
> Gabor
>
> Can you please describe a specific case or cases where ProcessorA and
> ProcessorB should be in the same package/module and yet have such vastly
>
+1 binding
On Mon, Sep 23, 2024 at 2:03 PM David Handermann
wrote:
>
> Team,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi NAR Maven Plugin 2.1.0.
>
> Please review the following guide for how to verify a release candidate build:
>
&g
the next 24 hours.
Here is the vote thread:
https://lists.apache.org/thread/2pvjony71jcfoqtxcx9y5wpnbzb1ofoo
Regards,
David Handermann
201 - 300 of 300 matches
Mail list logo
