+1 (binding)
Ran through the release helper, everything looks good.
Thanks David!
On Fri, Sep 20, 2024 at 3:45 PM Matt Burgess wrote:
>
> +1 (binding)
>
> Ran through release helper, verified successful build
>
> Apache Maven 3.9.9
> ]Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /
Thanks David. The proposal looks good to me and I definitely like the idea
of a separate NIP jira project, as well as separating nifi-api to its own
repo.
On Sat, Aug 31, 2024 at 10:36 AM Joe Witt wrote:
> Thanks David.
>
> Looks like a solid starting point.
>
>
> On Fri, Aug 30, 2024 at 8:15 PM
t; I think it will be especially useful for develop and test environments
> > where different versions of flows tend to be left on the canvas "just in
> > case we need more testing".
> >
> > Regards,
> >
> > Isha
> >
> > -Oorspronkelijk beric
All,
I'd like to propose a change to the flow synchronization behavior and
since we are still defining the new NIP process, I created a proposal
under the existing Feature Proposal page:
https://cwiki.apache.org/confluence/display/NIFI/Remove+MissingComponentsCheck+from+Flow+Synchronization
This
ke Thomsen
> wrote:
>
> The location info for the content repositories so I can monitor the free
> space.
>
> Our use case is a bit of a weird one driven by us having to hack around
> budget issues that aren't aligned with the expectations on the raw volume
> and size of
Processors should not know about nifi.properties.
What information are you trying to get?
On Tue, Aug 13, 2024 at 7:52 AM Mike Thomsen wrote:
> Is there a 1.X and 2.X safe way to get the configuration data from
> nifi.properties?
>
> Thanks,
>
> Mike
>
Hello,
The part in StandardVersionComponentSynchronizer is looping over
createdExtensions, but if you look at where things are added to that
collection, it is only adding processors, controller services, and
reporting tasks. The creation of parameter providers is actually in a
higher up layer in V
Hello,
Regarding not seeing the processor in the user interface, have you
enabled Python in nifi.properties?
# Uncomment in order to enable Python Extensions.
#nifi.python.command=python3
Thanks,
Bryan
On Tue, Jul 9, 2024 at 7:31 AM Cyrine ANENE wrote:
>
> Dear NiFi dev team,
>
> I hope this
Hello,
The session is like a transaction, so you can call session.transfer as
many times as you want, but nothing is actually transferred until you
call session.commit.
If you are extending from AbstractProcessor it handles this for you like this...
try {
onTrigger(context, session);
ses
Hello,
The provided nifi.properties should have three properties related to
python directories, the defaults are:
nifi.python.framework.source.directory=./python/framework
nifi.python.extensions.source.directory.default=./python/extensions
nifi.python.working.directory=./work/python
One of those
+1 binding
- Verified everything in release helper
- Built the referenced NiFi PR with the 2.0.0 plugin
- Verified one of the changes for attaching the manifest xml as a build artifact
Thanks Pierre!
On Wed, May 22, 2024 at 7:31 AM Pierre Villard
wrote:
>
> Hello Apache NiFi Community,
>
> I am
Thanks Pierre. I agree it would be good to kick out a release. I would
lean towards 1.6.0 since the commits seem to be improvements rather
than bug fixes for a patch.
On Mon, May 20, 2024 at 1:08 PM Pierre Villard
wrote:
>
> Hi all,
>
> We just merged a couple of improvements for the NiFi NAR Mav
+1 binding
- Verified everything in the release helper
- Ran into one issue with the new GitHub registry client [1] where it
is not honoring the selected branch when starting version control,
this only impacts the new UI where the branch selection was added, so
I don't think we have to block the r
+1 binding
Ran through release helper
Ran simple flow
Saved flows to registry, verified DB persistence is fixed
Thanks David!
On Fri, Jan 26, 2024 at 1:33 PM Robert Fellows wrote:
>
> +1 non-binding
>
> verified hashes
> build with java 21
> ran simple flow
> built with new UI
>
>
> On Fri, Jan
s way this would work with any registry implementation, not just the
> NiFi Registry (I'm saying this in case we ever get to a pure Git-based
> implementation of the Registry endpoint).
>
> Le mer. 17 janv. 2024 à 20:33, Bryan Bende a écrit :
>
> > Michael,
> >
> &
changes before they're
> committed, much like a pull request. Is this on the roadmap for Registry?
>
> Mike
>
> On Wed, Jan 17, 2024 at 4:14 PM Bryan Bende wrote:
>
> > Thanks guys, that makes sense in the context of the review model.
> >
> > Obviously some
processor is
> > configured with 50 concurrent tasks (for example). That would get deployed
> > in prod and potentially impact existing deployed flows. I guess one could
> > see this approach as a "checkstyle" plugin to allow or not the commit of a
> > new versi
I think before we embed something into synchronous API requests we
should try to define a few more real uses besides just a bucket naming
pattern to see if we really need to add something like this. For
bucket naming pattern, it could just be a simple property in
nifi-registry.properties with a reg
ood candidate for example).
> > >
> > > When you say it's adding a layer of complexity, it definitely does but
> > only
> > > for users that are looking for options when it comes to DR. In any case,
> > > setting up any piece of software to support DR scenarios
Just a couple of thoughts to add to the discussion...
The concept of the composite state manager really doesn't require any
framework level changes right? Even if we chose not to provide it out
of the box, it could still be implemented by anyone in a custom NAR.
For the state id, I do think this
+1 binding
Ran through the release helper and a sample flow, thanks Pierre.
On Fri, Nov 17, 2023 at 3:46 PM Joe Witt wrote:
> +1 binding
>
> Thanks everyone. Thanks Pierre!
>
> On Fri, Nov 17, 2023 at 1:39 PM Nissim Shiman
> wrote:
>
> > +1 (non-binding)
> >
> > verified source release sha25
Parameters are always stored in NiFi itself, encrypted in
flow.xml/flow.json. Parameter providers are a way to easily import
parameters and values from an external source like Vault and other various
secret stores, but they are still ultimately brought into NiFi and stored
locally.
NiFi Registry i
Hello,
Please try updating the version of the NAR Maven plugin you are using from
1.4.0 to the latest 1.5.1. I believe it will address this issue.
Your output shows:
org.apache.nifi:nifi-nar-maven-plugin:1.4.0:nar
Thanks,
Bryam
On Mon, Oct 30, 2023 at 2:14 PM Nguyen, Kyle
wrote:
> Hi there.
Hello,
We would need to see more information about the error besides that single
line, there should be a whole stacktrace that we would need to see.
Thanks,
Bryan
On Mon, Jul 31, 2023 at 9:49 AM Pallavi Metkar
wrote:
> Hi Team,
>
> I have upgraded the Apache NiFi cluster from 1.16.0 to 1.21.0
Hello,
It looks like your user has READ permissions to the resource, but not WRITE
permissions. You will need to check your access policies related to the
processor and/or the parent process group hierarchy.
Thanks,
Bryan
On Mon, Jul 31, 2023 at 8:09 AM Zhiyi Ni wrote:
> Hello, I have some qu
Hi Nissim,
I'm wondering if we need to store the set of sensitiveDynamicPropertyNames
in flow.json or flow.xml. Currently when loading the flow we are recreating
this set by looking at the property values and seeing which properties are
dynamic and have an encrypted value. The problem you are high
+1 (binding)
Verified signatures and hashes
Built plugin on MacOs with Java 11.0.16 and Maven 3.9.2
Built multiple projects with 1.5.1 plugin and verified issues from
NIFI-11324 no longer occur.
Thanks!
On Thu, Jun 15, 2023 at 8:53 AM Peter Turcsanyi
wrote:
> +1 (binding)
>
> Verified signatur
+1 Thanks Nandor, I agree it would be nice to get that fix out.
On Mon, Jun 12, 2023 at 10:05 AM Kevin Doran wrote:
> +1
>
> On Jun 12, 2023 at 05:35:57, Nandor Soma Abonyi
>
> wrote:
>
> > Hello Apache NiFi Community,
> >
> > I'd like to initiate a discussion about the next release of
> > nif
The processor has @TriggerWhenEmpty so it is going to keep executing
regardless of whether the incoming queue has data or not. I believe this
was done early on for some processors that used Kerberos in order to allow
the processor to have a chance to renew the Kerberos ticket, however we
since move
Hello,
You can add -verbose to the command to see a full error trace, however I'm
not sure it will tell you much more than the broken pipe message.
Broken pipe generally means some kind of network issue, typically it means
the other side of the connection closed the connection while the current
s
You are right, I didn't actually try to download it before, that is strange.
On Mon, Apr 10, 2023 at 1:07 PM Mike Thomsen wrote:
>
> When I clicked on it, I got a 404. Weird.
>
> On Mon, Apr 10, 2023 at 12:53 PM Bryan Bende wrote:
>
> > The Azure NAR looks like
The Azure NAR looks like it is there:
https://repo.maven.apache.org/maven2/org/apache/nifi/nifi-azure-nar/1.21.0/
On Mon, Apr 10, 2023 at 12:40 PM Mike Thomsen wrote:
>
> It’s failing on the azure one which is why I am raising the issue. I know we
> are still pushing that because it’s part of t
>>
>> We will attempt the advised approach and revert if we run into any
>> trouble.
>>
>> Thanks again!
>>
>> Regards,
>>
>> On Thu, 30 Mar 2023 at 16:49, Bryan Bende wrote:
>>
>>> Hello,
>>>
>>> This migh
Hello,
This might not give you exactly what you want, but the Minifi Toolkit
already has the ability to transform the JSON snapshot from registry,
there are actually two commands:
"transform" - for XML templates
"transform-vfs" - for versioned flow snapshot (JSON from registry) [1]
It doesn't pu
I lean towards option 2 with the caveat that maybe we don't have to
retain every Hadoop related component when creating this separate set
of components. Mainly I'm thinking that Hive has been the most
problematic to maintain so maybe that is dropped all together. I think
it would be unfortunate to
+1 binding
Everything checks out, thanks Kevin!
On Wed, Feb 1, 2023 at 5:52 AM Ferenc Erdei wrote:
>
> +1 Non binding
>
> Verified signatures and hashes
> - Built on OSX 13.1, with OpenJDK Runtime Environment (Temurin)(build
> 1.8.0_362-b09) Maven 3.8.3
> - Built NiFi with the new plugin versi
ugin 1.4.0
> > >
> > > Hi all,
> > >
> > > The issues raised on this thread have all been addressed, so I’d like to
> > > revive this goal to release NiFi NAR Maven Plugin 1.4.0 soon.
> > >
> > > Unless anyone is aware
The plan as I understand it is not to diverge and create separate feature
development on the 1.x line, so I would expect all PRs to continue to be
submitted only to main. We would release 1.x as needed with major bug fixes
or critical security updates, and these would be cherry-picked and/or
backpo
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 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
Thanks Kevin!
There is actually one change I was planning to start working on, and
since we don't release the NAR plugin very frequently, I would like to
try and get it in before this release.
I created this JIRA [1] for the issue, and I can report back here once
I start working on it to see if i
You would need to do the "Clone from Fork" step, having first forked
the repo in Github.
Then your "origin" would be your fork, and you can push anything you
want to your fork.
You won't have permissions to push anything to the apache repo with
your current setup.
On Thu, Sep 29, 2022 at 11:54 A
+1 (binding)
- Verified everything in release helper
- Ran basic flows
- Saved/imported flows with NiFi Registry
On Fri, Jul 29, 2022 at 2:50 PM Joe Skora wrote:
>
> +1 (binding) for release
>
> * helper guide review and build: hashes, certs, files checked out.
> * tested canvas and backend to c
ack to me. Yes, that’s correct we compiled with the
> ozone profile.
>
> G
>
> Sent from Proton Mail for iOS
>
>
> On Mon, Jul 25, 2022 at 18:12, Bryan Bende wrote:
>
> Hello,
>
> Did you build your own NiFi off 1.16.1 using the profile
> "include-hadoop-ozone&q
Hi Greg,
I don't really know anything about OpenTelemetry, but from the
perspective of integrating something into the framework, some things
to consider...
Is there some way to piggy-back on provenance and use a ReportingTask
to process provenance events and report something to OpenTelemetry?
If
Hello,
Did you build your own NiFi off 1.16.1 using the profile
"include-hadoop-ozone", and then used PutHDFS and that is what
generated the error in your attached logs?
-Bryan
On Mon, Jul 25, 2022 at 11:08 AM Giorgio wrote:
>
> Hello,
>
> I would like to report a potential bug that affects NiF
Apache NiFi Community,
I am pleased to announce that the Apache NiFi NAR Maven Plugin 1.3.5
release vote passes with:
5 +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 vote thread:
https://lists.apache.or
Hello Apache NiFi community,
Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.
# Download latest KEYS file:https://dist.apache.org/repos/dist/dev/nifi/KEYS
# Import keys file:
gpg --import KEYS
# [optional] Clear out local maven a
Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache
NiFi NAR Maven Plugin 1.3.5.
The source being voted upon, including signatures, digests, etc. can
be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.3.5/
The Git tag i
t;
> Thanks
>
> On Wed, Jul 20, 2022 at 12:38 PM Kevin Doran wrote:
>
> > +1 for cutting a release - thanks Bryan!
> >
> > On Jul 20, 2022 at 15:30:59, Bryan Bende wrote:
> >
> > > If there are no objections, I'm planning to kick out another minor
&
If there are no objections, I'm planning to kick out another minor
release for the NAR plugin to release a fix for a bug that was just
resolved [1] .
[1] https://issues.apache.org/jira/browse/NIFI-10253
I think you are right, it looks like in FlowParser parseJson, the
returned FlowInfo comes from this...
final VersionedProcessGroup rootGroup = dataflow.getRootGroup();
return new FlowInfo(rootGroup.getIdentifier(), ports);
Which I think should be the instance identifier there.
On Wed, Jul 13, 20
Hello,
What version of NiFi Registry are you trying to use with MariaDB?
There is a known issue in 1.16.0 that is addressed in 1.16.1:
https://issues.apache.org/jira/browse/NIFI-9950
Thanks,
Bryan
On Wed, May 11, 2022 at 2:44 PM John Wise wrote:
>
> We'd like to move from the built-in H2 da
ases to
> v1.15.3. Part of that is applying flow priorities all over the place in
> the new system. Probably not a common task, but I could see this feature
> being useful for other week-to-week work too.
>
> Ryan
>
> On Tue, Apr 12, 2022 at 1:32 PM Bryan Bende wrot
I think there are two different concepts here... The original
discussion is just about default settings for new connections. The
idea in NIFI-6831 is about prioritizing data across multiple queues,
either for all of nifi or within a given process group.
On Tue, Apr 12, 2022 at 1:13 PM Mark Bean
+1 (binding)
- Verified everything in release helper
- Ran a cluster and tested load-balanced connections, off-loading
data, and disconnecting/reconnecting nodes
On Thu, Mar 24, 2022 at 9:17 AM Robert Fellows wrote:
>
> +1 (non-binding)
>
> Verified signature
> Verified hashes
> Build on MacOS B
I left a comment on the JIRA, but all NARs are released to Maven
central on each release. The profiles just determine what is included
in the assembly. So users can still get any of the non-included NARs
by downloading it from Maven central, it just isn't obvious how to
find it.
On Mon, Mar 21, 20
/Contents/Home
> Build-Jdk:11.0.12
> Build-Jdk-Vendor:Eclipse Foundation
> Build-Arch:x86_64
> Build-Os:Mac OS X
> Build-Os-Version:11.2%
>
> On Fri, Mar 11, 2022 at 6:35 PM Nathan Gough wrote:
> >
> > I also ran into both of these issues. Though it was just a me
Mike,
What is the value of timestamp in your
nifi-manifest/nifi-runtime-manifest/target/classes/build.properties ?
On Fri, Mar 11, 2022 at 5:53 PM Mike Thomsen wrote:
> https://issues.apache.org/jira/browse/NIFI-9791
>
> On Fri, Mar 11, 2022 at 5:51 PM Mike Thomsen
> wrote:
> >
> > Will do
> >
Hello,
We just updated the link on the site a few days ago.
Can you try the "invite" link here?
https://nifi.apache.org/mailing_lists.html
Thanks,
Bryan
On Thu, Feb 10, 2022 at 8:46 AM Nathaneal James wrote:
>
> Hello,
>
> Is it possible to get an invite to the Apache Community Slack?
> I'm
Hello,
Regarding bundling the WAR, take a look at the update attribute NAR.
If you look at the expanded NAR after starting NiFi, it is located at
"work/nar/extensions/nifi-update-attribute-nar-1.16.0-SNAPSHOT.nar-unpacked/NAR-INF/bundled-dependencies"
you will see inside there is a ".war", so you
Hello,
1) I am not sure there is a definitive plan for removing variables
yet, but it is definitely something to consider for a NiFi 2.0 (or
other future release). I would also say that templates are in the same
situation.
Templates were created as a way for someone to share a part of a flow
with
Hello,
The GetSplunk processor has 3 time range strategies...
- Managed from beginning
- Managed from current
- Provided
The "managed" strategies store the last successful time range in
processor state, so when splunk is down it should keep trying to query
Splunk and failing and never updating t
s there a guide that one can use for creating
> file-based policy provider information in the authorizations.xml file?
>
> Best,
> Mike R
>
> On Tue, Dec 14, 2021 at 12:14 PM Bryan Bende wrote:
>>
>> CAUTION: This message is from an off campus source. Access to we
Hello,
The standard authorizer is composed of a user-group-provider and a
policy-provider. The LDAP user-group-provider can be be used to load
groups from LDAP, but you still need to define policies on them which
would be through a policy-provider, most likely the File-based
policy-provider which
I am pleased to announce that the 1.3.3 release of Apache NiFi NAR
Maven Plugin passes with
7 +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 PMC vote thread:
https://mail-archives.apache.org/mod_mb
t; >
> > Ran through the release helper. Looked great! Thanks for RMing Bryan!
> >
> > Matt
> >
> > On Thu, Dec 2, 2021 at 11:28 AM Matt Burgess wrote:
> >
> >> +1 (binding), ran through release helper and verified NARs were loaded
> >> successfully
Hello,
The standard release candidate verification helper can be found here:
https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
In addition, the following steps can be used to verify the improvement
made in this release...
1) Download the source
Hello,
I am pleased to be calling this vote for the source release of Apache
NiFi NAR Maven Plugin 1.3.3.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1188
The source being voted upon and the convenience bin
All,
I'd like to kick out a release of the NAR plugin to make a minor
improvement [1] available for the extension-manifest XML that is
generated during the build.
I can take care of putting together the release.
Thanks,
Bryan
[1] https://issues.apache.org/jira/browse/NIFI-9404
+1 (binding)
Verified everything in the release helper and tested saving/importing
flows to/from registry with inherited param contexts.
On Thu, Nov 4, 2021 at 5:56 AM Kotaro Terada wrote:
>
> +1 (non-binding)
>
> - Verified hashes.
> - Built from source with OpenJDK 8 and OpenJDK 11.
> - Run a
NiFi Community,
On behalf of the Apache NiFI PMC, I am very pleased to announce that
David Handermann has accepted the PMC's invitation to join the Apache
NiFi PMC.
David has made significant improvements in a number of security
related areas, he continues to improve the stability of our tests an
Hello,
The CLI doesn't currently have a command to set a property on a processor.
It would be a good one to add though, something like "proc-set-prop".
You could also figure out the call being made by performing the action in
the UI and looking at Chrome Dev Tools to understand the calls being ma
> > > > > the 2.x line. Maybe there are other workable models but my instinct
> > > > > suggests this is likely to follow a similar path.
> > > > >
> > > > > ...anyway I agree it isn't that easy of a call to dump Java 8
I'm a +1 for this... Not sure if this falls under "Removing Deprecated
Components", but I think we should also look at anything that has been
marked as deprecated throughout the code base as a candidate for
removal. There are quite a few classes, methods, properties, etc that
have been waiting for
+1
On Fri, Jul 16, 2021 at 2:31 PM Kevin Doran wrote:
>
> +1.
>
> > On Jul 16, 2021, at 2:28 PM, Joe Witt wrote:
> >
> > Yep definitely. Thought this was sorted via the JIRA.
> >
> > +1
> >
> > On Fri, Jul 16, 2021 at 11:26 AM David Handermann
> > wrote:
> >>
> >> Thanks for handling this, Matt
It was done as a precaution that a user may not realize that after
import or change-version, that the entire flow is going to
automatically start running. For cases where there is an existing flow
and the next version maybe adds one processor in the middle, it
probably wouldn't be a big deal, but t
Hello,
1) The folder structure in git is controlled by NiFi registry, so it
is not possible to create any different structure than what you are
seeing. Think of it like an internal database, you shouldn't really
need to know/care about the structure.
2a) Starting with NiFI 1.10.0 and registry 0.5
qBuilder.resolve(KrbAsReqBuilder.java:310)
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:447)
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:770)
> ... 95 common frames omitted
>
> On Wed, Mar 31, 2021 at 4:44 PM Derek R
So from a terminal on the nifi server, you can run "kinit
admin@MY.REALM" and enter the password and it works, and this same
principal and password entered into NiFi's login screen does not work?
On Wed, Mar 31, 2021 at 2:19 PM Derek Richardson wrote:
>
> I'm working on transitioning a nifi insta
+1 (binding)
- Verified everything in the standard release helper
- Setup secure standalone instance with SAML authentication
On Fri, Mar 12, 2021 at 10:17 AM Marton Szasz wrote:
>
> +1 (non-binding)
>
> Followed the release helper guide, tested the binary with a simple flow.
>
> Apache Maven 3.
I don't think it was the intent to pre-add a dynamic property. You
should be able to set a default value though, the user still has to
click the + icon to add the property though.
On Wed, Feb 24, 2021 at 12:02 PM Russell Bateman wrote:
>
> I have a dynamic property in a custom processor that my d
The available authentication mechanisms are...
- Client certificate
- Kerberos SPNEGO
- Keberos login identity provider
- LDAP login identity provider
- OpenID Connect
- Apache Knox SSO
- SAML (soon to be released)
You can also implement your own LoginIdentityProvider.
We currently don't provide
be
> > >> considered.
> > >>
> > >> Following on Joe's point about disabling plain HTTP, one option could be
> > >> generating both client and server certificates and using Mutual TLS for
> > >> authentication. This would obvi
two? I didn't find
> getting into developing with them a pain, but making me jump through the
> hoop of setting up LDAP may very well have changed that.
>
> These unsecure instances of NiFi out there are not our community's
> fault. I suppose we're worried about getting sp
I agree with the overall idea, although I would think it requires a
major release to make this kind of change to the default behavior.
Also, we have always avoided NiFi being a store of usernames and
passwords, so we don't have a login provider that uses a local file or
a database, we've always sa
+1 (binding)
- Verified everything in the release helper
- Tested enabling SAML authentication
Thanks Joe!
On Wed, Feb 3, 2021 at 1:10 PM karthick rn wrote:
>
> +1 (non-binding)
>
> Verified the signature & checksum
> Verified the build works on CentOS 8.2 (Azure VM), OpenJDK 11.0.9.1, Maven
>
You can open Chrome Dev Tools while using the UI and perform whichever
operations you are interested in on a parameter context and you can
see the requests made to the REST API.
If you are interested in REST API docs, there is a link on the left
side of the main docs page:
https://nifi.apache.org
Hello,
There are no plans to allow an extension (processor/cs/reporting task)
to change parameter contexts.
The REST API can be used to automate these tasks and there are already
commands in NiFi CLI to help make this easier...
nifi set-param
nifi delete-param
nifi list-param-contexts
nifi get-p
Since the beginning of the project our README has said "Maven >= 3.1",
which is obviously very old now. I was recently running into a problem
building main with Maven 3.3.9, that looks related to some new Maven
plugins in main depending on Maven 3.5.x apis. Switching to Maven
3.5.x resolved the iss
Hello,
1) I don't think NiFi currently supports the client id + x509
scenario, is this part of the OIDC standard? If so then maybe it can
be an improvement that is implemented.
2) The OIDC code in NiFi is not part of an extension point, so you
can't just plug in your own version. You would have t
Yea usually when you get RAT issues and the files referenced are in
target and other project related config files, it is because that
module was actually deleted and those files weren't under source
control so when you pulled the latest code it kept a copy of them
locally.
On Thu, Jan 14, 2021 at
This is expected behavior...
Saving or pulling the flow is happening on behalf of the end user in
nifi which is being proxied by the nifi server over to registry. In
this case, the nifi server only needs proxy permissions.
Checking the status of all the versioned PGs happens in the background
as
Hello,
I have added you as a contributor in JIRA.
Thanks,
Bryan
On Wed, Dec 9, 2020 at 10:45 AM Marton Szasz wrote:
>
> Hi,
>
> You can subscribe to the lists by sending an email to the subscribe
> address, dev-subscr...@nifi.apache.org in this case.
>
> I can't add you to Jira but I'm sure so
Hello,
We need to add documentation around this, but right now you can see
examples in the JIRA which added these commands:
https://issues.apache.org/jira/browse/NIFI-6112
Thanks,
Bryan
On Thu, Dec 3, 2020 at 10:31 AM Huan Yan wrote:
>
> Hello,
>
> I am currently trying to make a controller s
Hello,
Please don't label things as "urgent". This is a place to get free
help, and if someone knows the answer to your question, then they will
respond whenever they have time.
Thanks,
Bryan
On Wed, Dec 2, 2020 at 4:11 AM Chris Sampson
wrote:
>
> To change the setting, if that's what you're a
Hello,
I have added you as a contributor, you should be able to assign
yourself tickets now.
Thanks,
Bryan
On Wed, Dec 2, 2020 at 8:21 AM David Handermann
wrote:
>
> Hi Cory,
>
> Thanks for submitting the issue and requesting access to Jira, I'm sure one
> of the project maintainers will be ab
Chris,
The illegal reflective access warnings are expected when running on Java 11.
The second warning about the provenance repo seems like a possible
issue due to some recent refactorings made for stateless, we should
take a look at that.
Thanks,
Bryan
On Tue, Dec 1, 2020 at 3:58 AM Chris Sam
Regarding adding support for expression language...
You could use parameter contexts instead of variables, all properties
can reference parameters by default so no need to update property
descriptors, just set to #{SearchRecursively} to reference the
parameter.
In my opinion this would be better
Hello,
Since the dynamic properties of InvokeHttp are not marked as sensitive
properties, there currently isn't a way to add a sensitive header
value.
There is a JIRA to improve this experience -
https://issues.apache.org/jira/browse/NIFI-7310
Thanks,
Bryan
On Thu, Nov 5, 2020 at 11:02 AM Midh
1 - 100 of 894 matches
Mail list logo
