Russell,
I'm not sure how to fix the relationships, but in flow.json.gz and flow.xml.gz,
scheduledState could be changed from RUNNING to ENABLED for each of these
processors and these messages shouldn't appear on startup.
Just to be clear, this is an unsupported operation, with potential for u
+1 (non-binding)
checksum looks good
Compiled with
Apache Maven 3.9.10
Java 21.0.7 (openjdk)
RHEL 8
Ran various simple flows.
Ported registry from 2.4.0 to this version successfully. Imported from NiFi
registry to NiFi, Updated PG and saved back to registry successfully.
Verified reso
+1 (non-binding)
checksum looks good
Compiled with
Apache Maven 3.9.10
Java 21.0.6 (openjdk)
RHEL 8
Verified https://issues.apache.org/jira/browse/NIFI-7123 Add documentation to
onPropertyModified() to describe how it is called
Thank you David for RM'ing.
Nissim
On Friday, July 11,
Thank You, Joe!
On Friday, May 2, 2025 at 01:03:25 PM EDT, Joe Witt
wrote:
Added a simple comment. Seems fine otherwise and my comment was very
trivial.
Thanks
On Fri, May 2, 2025 at 9:47 AM Nissim Shiman
wrote:
> Hello Team,
> Could someone review the PR for
&
Hello Team,
Could someone review the PR for https://issues.apache.org/jira/browse/NIFI-7123
It is just a javadoc update to reflect current behavior for
onPropertyModified()
Thanks,
Nissim
+1 (non-binding)
checksum looks good
Compiled with Apache Maven 3.9.9 Java 21.0.6 (openjdk) RHEL 8
Set up on cluster of three nodes. Ran various simple flows. Ported registry
from 2.1.0 to this version successfully. Imported from NiFi registry to
cluster, Updated PG and saved back to regi
+1 (non-binding)
checksum looks good
Compiled withApache Maven 3.9.9Java 21.0.6 (openjdk) RHEL 8
Verified new javadoc for DisallowRunOnce annotation (
https://issues.apache.org/jira/browse/NIFI-14371 )
Thank you, David, for the new release.
Nissim Shiman
On Friday, March 28, 2025 at 04
vid for doing the release.
Nissim Shiman
On Friday, December 20, 2024 at 08:46:50 PM UTC, David Handermann
wrote:
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.1.0.
Please review the following guide for how to verify a release candidate build:
Hello Team,
I am running into an issue when running on a three node cluster. If the ui is
brought up on one of the non-primary nodes, and refreshed, it give an error:
Invalid State
Current state = CODING_END, new state = CODING
I am interested if others see anything similar.
Code was compile
.1 release happened
> > >
> > > On Fri, Nov 15, 2024 at 3:52 PM Dan S wrote:
> > > >
> > > > I can take care of this.
> > > >
> > > > On Fri, Nov 15, 2024 at 9:22 AM Nissim Shiman
> > > >
> > > > wrote:
> >
Team,
I'm not sure if the Netty upgrade PR
https://issues.apache.org/jira/browse/NIFI-14010 has been backported the to the
1.28.x branch yet.
Do we still want this now or is getting in before the final Dec 8 build good
enough?
Thanks,
Nissim
On Friday, November 15, 2024 at 10:47:06 A
.
Thank you Ferenc and team for the upcoming release.
Thanks,
Nissim Shiman
On Tuesday, October 22, 2024 at 10:45:12 AM UTC, Ferenc Kis
wrote:
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.28.0.
Please review the following guide for how to verify
Matt for verifying
this.
Thank you David and team,
Nissim Shiman
On Wednesday, October 23, 2024 at 05:55:18 PM UTC, Matt Gilman
wrote:
Thanks for reporting this Nissim. I've filed [1] to track the issue.
Matt
[1] https://issues.apache.org/jira/browse/NIFI-13926
On Wed, Oct 23,
first choice on the dropdown,
then it is not able to be imported to the nifi ui.
The ui message will be:
The Flow Registry with ID reports that no Flow exists with Bucket ,
Flow Version
I am wondering if anyone else is seeing this.
Thanks,
Nissim Shiman
On Tuesday, October 22, 202
!
Nissim Shiman
On Thursday, September 19, 2024 at 06:43:33 PM UTC, David Handermann
wrote:
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
team for the upcoming release.
Thanks,
Nissim Shiman
On Wednesday, July 3, 2024 at 12:42:40 PM UTC, Pierre Villard
wrote:
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.27.0.
Please review the following guide for how to verify a release candidate
+1 (non-binding)
checksums look good
Compiled withApache Maven 3.9.8 Java 21.0.3 (openjdk) RHEL 8
Set up/ran site-to-site flow and some rest api calls
Thank you David and team,
Nissim Shiman
On Friday, June 28, 2024 at 09:40:57 AM EDT, David Handermann
wrote:
Team,
I am pleased
INFO [main]
o.a.n.registry.bootstrap.RunNiFiRegistry NiFi Registry never started. Will not
restart NiFi Registry
Thanks,
Nissim Shiman
On Thursday, June 27, 2024 at 09:01:30 PM UTC, Pierre Villard
wrote:
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.27.0.
Please review the
- Processor change history on property hover
Thank you Pierre and team for 1.26.0!
Nissim Shiman
On Friday, May 3, 2024 at 12:47:45 PM UTC, Pierre Villard
wrote:
Team,
I am pleased to be calling this vote for the source release of Apache NiFi
1.26.0.
Please review the following guide for
ioned flow with component that migrates
properties, controller service reference is invalid
NIFI-12666 Correct NiFi Registry Data Source Configuration
Thank you David and team for the upcoming release!
Nissim Shiman
On Friday, January 26, 2024 at 02:30:45 AM UTC, David Handermann
wrote:
T
rom 1.24.0 or 2.0.0 M1 to this RC
as well (i.e. the registry starts up, but doesn't see any of the
buckets/versioned flows)
Thanks,
Nissim Shiman
On Wednesday, January 24, 2024 at 10:35:34 AM EST, David
Handermann wrote:
Team,
I am pleased to be calling th
upcoming release!
Nissim Shiman
On Tuesday, November 21, 2023 at 10:40:25 PM UTC, David Handermann
wrote:
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
Nissim Shiman
wrote:
>
> Team,
>
>
> I'm having difficulty migrating from registry 1.22.0 or earlier to 2.0.0-M1.
> This was not seen on when moving to 1.24.0 (RC3).
>
>
> i.e. Migrating registry from 1.23.2 to 2.0.0-M1 or 1.24.0 (RC3) works fine.
>
>
&
.start(FileStore.java:916) at
org.h2.mvstore.MVStore.(MVStore.java:289) at
org.h2.mvstore.MVStore$Builder.open(MVStore.java:2035) at
org.h2.mvstore.db.Store.(Store.java:133) ... 136 common frames
omitted
Thanks,
Nissim Shiman
On Tuesday, November 21, 2023 at 10:40:25
when PG was copied from a version controlled PG
Thank you Pierre and team for the upcoming release!
Nissim Shiman
On Friday, November 17, 2023 at 08:10:20 PM UTC, Dan S
wrote:
+1 (non-binding)
- Went through the Release Candidate Verification
<https://cwiki.apache.
/browse/NIFI-11872
Verified these issues where in existance in prior releases as well. Not
blockers.
Thank you David and team for the upcoming release!
Nissim Shiman
On Friday, July 28, 2023 at 03:57:25 PM UTC, Ferenc Kis
wrote:
+1 (non-binding)
Went through the helper guide, full
It is not so common to have components in ghost state, and
only some of them allow Dynamic Properties so this is an acceptable risk
considering the alternatives.
I am interested in community feedback and/or other suggestions to the current
situation.
Thanks,
Nissim Shiman
blocker.
Also, noticed that MonitorMemory has difficulty running when scheduled as a
cron.Created https://issues.apache.org/jira/browse/NIFI-11661Also not a blocker.
Thank you for the upcoming release!
Nissim Shiman
On Tuesday, June 6, 2023 at 09:38:43 PM UTC, Joe Witt
wrote:
Hello,
I am
d.
>
> [1] - https://issues.apache.org/jira/browse/NIFI-11560
>
> Thanks,
> -- Mike
>
>
> On Wed, May 24, 2023 at 2:13 PM Nissim Shiman
> wrote:
>
> > Joe and team,
> >
> > Thank you for the coming release.
> > I am hoping someone can review/commit
> &
and mosermw for previous recent
reviews/merging of tickets I was working on)
Thanks,
Nissim Shiman
On Wednesday, May 24, 2023 at 12:57:42 PM EDT, David Handermann
wrote:
Joe,
Thanks for initiating the discussion, I agree that the number of bug fixes,
dependency upgrades, and other
Hello apache nifi committers,
Could someone review https://issues.apache.org/jira/browse/NIFI-10756
StandardSSLContextService will fail silently on nifi restart if keystore no
longer exists
I would very much appreciate it.
Thanks,
Nissim Shiman
Controller Service Details's Settings tab)
are sometimes not working. Made NIFI-11389 for this. Not a blocker.
Thank you for upcoming release!
Nissim Shiman
On Tuesday, April 4, 2023 at 12:11:38 AM UTC, Joe Witt
wrote:
Hello,
I am pleased to be calling this vote for the source re
well. nifi screen looses look and feel when this occurs and displays
OutOfMemoryError
Put in a jira for this https://issues.apache.org/jira/browse/NIFI-11153
This would be a very limited user initiated edge case, so I don't think this is
a blocker.
Thank you for the upcoming releas
descriptor)
I would greatly appreciate that as well.
Thanks,
Nissim Shiman
On Thursday, December 8, 2022 at 01:40:40 PM EST, Nissim Shiman
wrote:
Hello apache devs,
Could someone review/merge:
https://issues.apache.org/jira/browse/NIFI-10608 Copied Processor Group no
longer
,
Nissim Shiman
gz (I guess from before nifi
1.16) this might be noticed.
Will put in a jira for this edge case.
Thank you for the upcoming release!
Nissim Shiman
On Wednesday, November 23, 2022 at 03:58:27 PM UTC, Joe Witt
wrote:
Hello,
I am pleased to be calling this vote for the source release of A
Joe,
Sorry for the previous brevity, but for example:
create new PG -> right click -> Configure -> Controller Sevices -> Add any
controller service (AvroReader for example)
copy PG
new PG -> right click -> Configure -> Controller Services -> (new controller
service will be not listed/ AvroReader
+1 (non-binding)
verified source release sha256/512 checksums
built and ran successfully using:Apache Maven 3.6.3 Java openjdk version:
1.8.0_332
linux kernel 3.10.0-1160
verified out of the box simple invokeHTTP to ListenHTTP flow
put simple invokeHTTP to ListenHTTP flow in process group,
Hello apache nifi devs,
Resending request ... in hopes of still making 1.18
Thanks,
Nissim
On Monday, September 19, 2022 at 03:52:49 PM EDT, Nissim Shiman
wrote:
Hello apache nifi committers,
Could you look at two bug fixes:
https://issues.apache.org/jira/browse/NIFI-9878
python
These have relatively modest amount of code changes and have already been
reviewed.
Thanks,
Nissim Shiman
Hello nifi devs,
Are we aware of a location for an implementation of the Load Distribution
Service api [1] ?
This is used in the DistributeLoad processor [2], but is not found when chosen.
I searched the nifi code for an implementation and there doesn't appear to be
one. Maybe it is in a su
Hello Apache NiFi team,
Resending below email with request to review/commit
PR: https://github.com/apache/nifi/pull/6035
It already has a review with +1, but is waiting on a committer to look at it.
Thanks,
Nissim
On Thursday, May 19, 2022, 02:55:40 PM EDT, Nissim Shiman
wrote
users to have finer control over bulletin levels (i.e. settings of NONE,
DEBUG, INFO, WARN, ERROR) just like processors currently allow.
I think this functionality will be useful for many nifi users.
This has already been reviewed.
Thanks,
Nissim Shiman
Hello NiFi devs,
Do we know if there is way to turn off bulletins for controller services?
Processors have Bulletin level configurable on the "Settings" tabs, but it is
not clear there is similar functionality exposed for controller services
Thanks,
Nissim
ive Thread Count" is more comprehensive and includes has other threads as
well (i.e. reporting tasks etc.)
Is this correct?
And do we know the various other sources that nifi threads can come from
besides processors that "Active Thread Count" captures?
Thanks,
Nissim Shiman
s (when dealing with non-FFv3 data) as well
as incoming attributes (when dealing with FFv3 data)
Thank You,
Nissim Shiman
NIFI-7738 https://issues.apache.org/jira/browse/NIFI-7738 (Provenance Search
Events - add feature to allow inverse query) has had PR updated based on
comments.
It would be very much appreciated if this could make it into 1.13.0 as well
Thanks,
Nissim
On Tuesday, January 12, 2021, 01:58:30
.
Also, thank you Mark Payne for merging NIFI-7225 and commenting on NIFI-7738!
Thank You,
Nissim Shiman
On Monday, December 28, 2020, 12:25:25 PM EST, Nissim Shiman
wrote:
Hello apache nifi devs,
I have thoroughly reviewed and tested PRs for 2 bug related tickets (both on
java 8 and
that has been reviewed and tested by another contributer as well.
So no additional reviewing/testing needs to be done by a PMC/committer as they
have been vetted.
Could someone commit these to main?
Thank You!
Nissim Shiman
Hello Nifi Team,
NIFI-7738 [1] https://github.com/apache/nifi/pull/4563
has already been reviewed/tested by a fellow contributer
I would greatly appreciate a committer moving this to main for 1.13.0
Thanks,
Nissim Shiman
[1] https://issues.apache.org/jira/browse/NIFI-7738
On Sunday
and
> >then add another validator that checks for the existence of a folder
> >and that it is a folder, not a file.
> >
> >Thanks,
> >
> >Mike
> >
> >On Thu, Nov 19, 2020 at 1:06 PM Nissim Shiman
> > wrote:
> >>
> >> Hello N
/nifi-commons/nifi-utils/src/main/java/org/apache/nifi/processor/util/StandardValidators.java#L505[2]
https://github.com/apache/nifi/blob/main/nifi-commons/nifi-utils/src/main/java/org/apache/nifi/processor/util/StandardValidators.java#L851-L852
Thanks,
Nissim Shiman
ready noticed
this conversation and has already reviewed my PR and has made some useful
comments. So we are already seeing results. (and thank you Mark!)
I plan to start reviewing/testing PRs.
Thank You,
Nissim Shiman
On Thursday, October 8, 2020, 12:17:13 PM EDT, Joe Witt
wrote:
Hello
A
Second attempt...
Hello NiFi team,
Could someone respond to this email.
Thanks,
Nissim Shiman
On Monday, October 5, 2020, 11:01:57 AM EDT, Nissim Shiman
wrote:
Hello NiFi team,
Could someone review the pull request for NIFI-7738
(https://issues.apache.org/jira/browse/NIFI-7738
ories) and
VolatileProvenanceRepository.java
The rest are just involved in propagating the ability to query the "NOT" option
for a given user entered provenance search value from the gui to the backend
query.
Thank You,
Nissim Shiman
the user is indicating to do an inverse query for the value
entered.)
I put together a proof of concept and it works without any obvious complexity
or gotcha issues.
What do you think about this?
Thank You,
Nissim Shiman
[1]
https://github.com/apache/nifi/blob/main/nifi-nar-bundles/n
.
This way the final merge is still done by a committer, but the review step has
already been handled.
Thanks,
Nissim SHiman
/ConfigurableComponent.java#L68
Thanks,
Nissim Shiman
Could someone look at merging in NIFI-6851
https://issues.apache.org/jira/browse/NIFI-6851
Thanks,
Nissim Shiman
On Monday, January 6, 2020, 12:06:06 PM EST, Joe Witt
wrote:
Team,
We've already seen a good stream of nice fixes, improvements, and some
minor features land on
Hello Apache Nifi team,
I would like to request jira contributer access to apache nifi. I would like
to work ticket NIFI-6851.
My jira username is:Nissim Shiman
Thanks,
Nissim Shiman
specified it would be UNSPECIFIED.
I dont think this needs to be on the flowfile attribute - it would go
straight to the provenance event itself which is generated by the session.
Thanks
Joe
On Wed, Nov 6, 2019 at 11:32 AM Nissim Shiman
wrote:
> Joe,
>
> Just to verify what you mean,
&g
ay, November 4, 2019, 12:50:11 PM EST, Nissim Shiman
wrote:
Having an attribute added indicating passive/active/query for RECEIVE and
FETCH will work,
but nifi attributes are stateful (i.e. they will still be on the flowfile as
metadata a couple of processor steps down the flow)
Maybe an
Nissim Shiman
wrote:
> Mike,
> I like the QUERY type as well. Basically a more refined PULL. Very nice.
>
>
> Part of the challenge of adding PULL as a type is that there are currently
> two flavors of RECEIVEs.
> RECEIVE and FETCH [1]
>
> So any addition of a PULL wo
Http
QUERY - Go looking for the data and take what matches your search. Ex.
JsonQueryElasticsearch, GetMongo, any SQL query processor, etc.
On Wed, Oct 30, 2019 at 1:31 PM Nissim Shiman
wrote:
> Joe,
>
>
> It is hard to say how much value transit URI would bring to clarify a
>
here that is all opt-in for existing
users and components.
Thanks
On Tue, Oct 29, 2019 at 9:41 AM Nissim Shiman
wrote:
> Adam,
> good points...
> I missed a step in explaining the use case where Provenance Events is
> incomplete...
> Where the second nifi does a GetSFTP from the *
m/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpResponse.java#L191
On Mon, Oct 28, 2019 at 4:47 PM Nissim Shiman
wrote:
> Adam,
> I believe there is a need for more detailed ProvenanceEv
ot;However even more important to realize,
this change would affect many other downstream consumers of provenance data
which aren't necessarily in the stock NiFi distribution."
Thanks,
Nissim
On Friday, October 11, 2019, 11:30:19 AM EDT, Nissim Shiman
wrote:
Adam,
"Yes&q
bly need for a strong vision to
help demonstrate the value for this vs. the cost of the cascading effects
related to this change.
Thanks,
Adam
On Thu, Oct 10, 2019 at 4:02 PM Nissim Shiman
wrote:
> Hello Team,
>
> The ProvenanceEventType class does a good job capturing possible events,
&g
more accurately capture the event.
Thanks,
Nissim Shiman
69 matches
Mail list logo
