+1 (non-binding)
Verified signature and hashes.
Performed full build starting from an empty local maven repo.
Maven: 3.9.6
Java 21.0.2, Eclipse Adoptium
Ubuntu 24.04.4
Installed binary and started NiFi with all default settings. Ran simple
flow and interacted with the UI, looked at metrics,
+1 (non-binding)
Verified keys and hashes
Performed a clean build
Java 1.8.0_402
Maven 3.9.3
Ubuntu 22.04.4
Performed upgrade from NiFi 1.25.0
Started correctly. Interacted with NiFi Registry 1.25.0 normally.
Performed upgrade of NiFi Registry from 1.25.0
Again, behavior and interaction between
I think you may be hitting a bug that was introduced in NiFi 1.25.0. See
https://issues.apache.org/jira/browse/NIFI-12785
This issue has been resolved and will be fixed in NiFi 1.26.0.
On Thu, Apr 11, 2024 at 1:55 PM Martin Fong wrote:
> We have installed 1.25.0 and there is no deprecated
Try adding your EC2 instance's private IP address mapping to public DNS
name in /etc/hosts. And, in that case, you can use
nifi.web.https.host=
-Mark
On Thu, Mar 28, 2024 at 4:40 PM Joe Witt wrote:
> Mark
>
> I believe you will need to tell NiFi you want it to listen on more than the
>
+1 (non-binding)
Verified signature and hashes
Performed complete build with -Pcontrib-check
Maven 3.9.3
Java 1.8.0_392 (OpenJDK)
Ubuntu 22.04.3
Installed NiFi in different scenarios:
- default configuration (single-user)
- customized configuration (admin user) but no flow
- upgrade
+1 (non-binding)
Verified signature and hashes
Performed complete build with -Pcontrib-check
Maven 3.9.3
Java 21.0.2 (Eclipse Adoptium)
Ubuntu 22.04.3
Installed NiFi in different scenarios:
- default configuration
- customized configuration (admin user) but no flow
- upgrade from
+1 (non-binding)
Verified signature and hashes
Built source code with Java 8 and 11 on Ubuntu 22.04.3 LTS
openjdk version "1.8.0_382"
openjdk version "11.0.20.1" 2023-08-24
Installed NiFI Registry as an upgrade from an older Registry more than one
version away (1.18.0)
Installed NiFi as an
+1 (non-binding)
Downloaded source and confirmed keys and signature.
Built source from empty local maven repo and using -Pcontrib-check for each
Java version:
openjdk version "1.8.0_382"
openjdk version "11.0.20"
openjdk version "17.0.8"
Maven, 3.9.3
Ubuntu, 22.05.3 LTS
Installed NiFi and
I was working on a very similar response. Thanks Joe for the clear
articulation. I agree with this approach 100%.
Adding one additional point, the differentiation of Java 17 in the NiFi 2.0
line may encourage and expedite the migration to a new major release. I
think we want to get there as soon
+1 (non-binding)
Verified signature and hashes
Built source code on Ubuntu 20.04.2 using -Pcontrib-check and an empty
local repo each time
- openjdk version "1.8.0_362"
- openjdk version "11.0.19"
- openjdk version "17.0.7"
Performed upgrade installation of both NiFi and NiFi Registry
-1 (non-binding)
Discovered an H2 database migration issue in NiFi Registry when attempting
to upgrade from 1.22.0 to 1.23.0. Thanks David Handermann for reproducing
and confirming.
JIRA created
https://issues.apache.org/jira/browse/NIFI-11845
On Thu, Jul 20, 2023 at 8:16 PM David Handermann <
The flow.xml.gz/flow.json.gz has the (now removed) properties as part of
the definition. Therefore, they still appear on the updated processor, but
now as dynamic properties. The only recourse is to remove the properties
from existing processor instances, or to delete the processor and
instantiate
+1 (non-binding)
Downloaded source and performed checksum validation
Built with empty maven repo on Ubuntu 22.04.2, maven version 3.6.3
Repeated build with unit tests using the following versions of Java
- openjdk version "1.8.0_362"
- openjdk version "11.0.19" 2023-04-18
- openjdk version
+1 (non-binding)
Verified signatures and hashes.
Performed full build with -Pcontrib-check using maven 3.6.3 and Java
11.0.18 on Ubuntu 20.04.1.
Installed and ran NiFi again using Java 11.0.18. Executed some basic flows.
On Mon, Apr 3, 2023 at 8:11 PM Joe Witt wrote:
> Hello,
>
> I am pleased
If the expected documentation is not showing up in the UI - particularly if
an older version of the documentation is present - you may have to clear
your browser cache and reload the documentation page.
-Mark
On Wed, Apr 5, 2023 at 11:52 AM Matthew Baine
wrote:
> Hi Russell and Bryan,
>
> Yes,
n/m.. I missed the vote results email. I had thought voting was open for 3
days.
On Fri, Mar 17, 2023 at 8:29 AM Mark Bean wrote:
> I get a 404 error when attempting to download the source.
>
> -Mark
>
> On Tue, Mar 14, 2023 at 4:59 PM Kevin Doran wrote:
>
>> Hel
I get a 404 error when attempting to download the source.
-Mark
On Tue, Mar 14, 2023 at 4:59 PM Kevin Doran wrote:
> Hello Apache NiFi Community,
>
> Issues with RC1 have been addressed in RC2, and I am pleased to again
> be calling this vote for the source release of Apache NiFi NAR Maven
>
+1 (non-binding)
On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi
I agree this is a great start to a discussion with pointers to important
docs for the 2.0 transition. Thanks David!
Mike - what do you mean by "controller service-based configuration for
connection details"?
Also, the transition from Java 11 to 17 is not without potential issues.
I've discovered
+1 (non-binding)
Verified checksums and signatures.
Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, 11.0.17,
17.0.5
Installed, configured and ran NiFi and NiFi registry testing several flows
and Registry functions. During testing, verified NIFI-10939 and NIFI-10937
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?
Is it detecting duplicates only within a given NAR or across multiple NARs?
Thanks,
Mark
On Tue, Nov 29, 2022 at
+1 (non-binding)
Verified checksums and signatures.
Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, 11.0.17,
17.0.5
Ran several relatively simple flows in non-cluster mode only. No issues
observed.
I don't believe this is worth holding up the 1.19.0 release, but while
meantime.
>
> Regards,
> Matt
>
> On Tue, Nov 15, 2022 at 4:42 PM Nathan Gough wrote:
> >
> > We might also want https://issues.apache.org/jira/browse/NIFI-10787
> >
> > On Tue, Nov 15, 2022 at 4:05 PM Mark Bean wrote:
> >
> > > I will be on it in abo
I will be on it in about 2 hours, if not addressed sooner.
On Tue, Nov 15, 2022 at 3:46 PM Joe Witt wrote:
> NIFI-10703 would be great to get in. Just a matter of gettin' it done and
> merged I think. You're on it?
>
> Thanks
>
> On Tue, Nov 15, 2022 at 1:38 PM Mark Bean
Sorry.. check that. There's a typo in the latest commit on that PR.
On Tue, Nov 15, 2022 at 3:35 PM Mark Bean wrote:
> Could we get NIFIDEVS-10703 (PR #6638) in there too? AFAIK, it's good to
> go.
>
> Thanks,
> Mark
>
>
> On Tue, Nov 15, 2022 at 2:56 PM Joe Witt wrote:
Could we get NIFIDEVS-10703 (PR #6638) in there too? AFAIK, it's good to go.
Thanks,
Mark
On Tue, Nov 15, 2022 at 2:56 PM Joe Witt wrote:
> Hello All,
>
> I plan to kick off the RC as soon as
> https://issues.apache.org/jira/browse/NIFI-10701 is merged.
>
> Thanks
>
> On Thu, Nov 10, 2022 at
Community,
Looking for a little help on several PR's that have been open, one since
July.
NIFI-4798 allow empty value for UpdateAttribute property
https://github.com/apache/nifi/pull/6585
NIFI-10243: allow ControlRate to throttle on combination of data rate or
flowfile rate
> > admin to change to the new property.
> >
> > Alternatively, the deprecated property could be hidden if a new method
> was
> > implemented in a processor that changed old property values to new ones
> (in
> > this case converting 10 to “10 Mb”.
> >
> > Just a th
I am working on NIFI-10243 [1]. The goal is to allow ControlRate to
throttle based on both data rate and FlowFile count. If either rate is
exceeded, throttling occurs.
Currently, throttling occurs in only one mode. Therefore, a single
property, Maximum Rate, is overloaded to accept either a size
Downloaded source and verified keys and signatures
Performed full build including contrib-check using:
OpenJDK Runtime Environment (build 1.8.0_342-8u342-b07-0ubuntu1~22.04-b07)
OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu122.04)
OpenJDK Runtime Environment (build
Downloaded source and verified keys and signatures
Performed full build including contrib-check using:
OpenJDK Runtime Environment (build 1.8.0_342-8u342-b07-0ubuntu1~22.04-b07)
OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu122.04)
OpenJDK Runtime Environment (build
Is there a way to programmatically update parameters in a
parameter context, i.e. modify parameter values within a processor? If
there parameters are not visible to the onTrigger method for using in a
custom processor, would InvokeHTTP be an advisable approach?
Thanks,
Mark
;
> final VersionedProcessGroup rootGroup = dataflow.getRootGroup();
> return new FlowInfo(rootGroup.getIdentifier(), ports);
>
> Which I think should be the instance identifier there.
>
> On Wed, Jul 13, 2022 at 11:57 AM Mark Bean wrote:
> >
> > When starting NiFi for the first
When starting NiFi for the first time using the managed-authorizer, NiFi
will put the Initial Admin Identity in certain Access Policies. However, it
only does this for Global Access Policies, and does not add this user to
any Component Access Policies, e.g. 'view/modify the component'.
This has
if this is a load balancer related issue or
something else.
On Fri, Jun 10, 2022 at 3:13 PM Mark Bean wrote:
> Yes, it will be a few weeks at least to get the upgrade into the
> environment where we see this occurring and eavluate. Part of the problem
> is reproducibility. We haven't ye
; be addressed in that fix which went into the release 6 months ago and is
> > also in the 1.16.x line. You'll want that and of course the many other
> > improvements to have improved behavior for this scenario.
> >
> > Thanks
> >
> > On Fri, Jun 10, 2022 at 10:
nto 1.16.2.
On Fri, Jun 10, 2022 at 1:31 PM Mark Payne wrote:
> Mark,
>
> This is a manifestation of NIFI-9433 [1] that we fixed a while back.
> Recommend you upgrade your installation.
>
> Thanks
> -Mark
>
>
> [1] https://issues.apache.org/jira/browse/NIFI-9433
>
We have a situation where several flowfiles have lost their content. They
still appear on the graph, but any attempt by a processor to access content
results in a NullPointerException. The identified content claim file is in
fact missing from the file system.
Also, there are ERROR log messages
, 2022 at 12:41 PM Mark Bean wrote:
> I added 'metadata.max.age.ms = 1000' to the ConsumeKafka_2_6 processor.
> It started receiving faster than the ConsumeKafka_2_6 (which has not
> received any messages after about 15 minutes.) Here's my observations (all
> with different Cons
Knowles
>
> On Fri, May 27, 2022 at 9:27 AM Mark Bean wrote:
>
> > I do not see this property (metadata.max.age.ms) anywhere in the
> > ConsumeKafka processor. If I want to adjust this value to something less
> > than 5 minutes, that will mean modifying th
adata.max.age.ms}
> configuration: by lowering
> * the max metadata age, the consumer will refresh metadata more often
> and check for matching topics.
>
>
> I would wager you're running into this lag above due to the pattern only
> checking every five minutes by default.
>
>
I have two ConsumeKafka_2_6 processors (NiFi 1.16.1). The first uses Topic
Name Format of "names". The second uses Topic Name Format of "pattern". The
names format is able to sync with Kafka relatively quickly and begins
receiving messages within just a couple seconds. However, the pattern
format
; > > > 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
We experimented with the idea of a custom "Global Prioritizer". One of the
problems with this approach is that it ran the risk of breaking the
multi-tenancy philosophy. If there were a truly global priority, it would
affect all flows, each may have different priority rules. However, if this
could
+1 (non-binding)
Ran through steps in the helper guide. Built with various versions of Java:
8, 11 and 17. All were successful.
Single instance, simple flow behaved as expected. Would like to run in a
cluster environment, but may not have time to set that up before voting
closes.
On Mon, Mar
Joe,
I just discovered an issue yesterday that might need attention first. I
haven't investigated fully yet nor created a ticket because I don't yet
fully understand it. However, it appears as though the
single-user-authorizer may not be behaving as intended. When I updated
nifi.properties to
Is anyone else having trouble building NiFi (main) on macOS? I recently
upgraded to macOS Monterey 12.1 and since then I have not been able to
build NiFi. I'm not sure if the failure started exactly coincidental with
the macOS upgrade, but it stands out as a significant recent change.
I get an
+1 (non-binding)
Verified keys and checksums
Successfully built (MacOS 11.5.2, Java 1.8.0_282)
Checked that README, NOTICE and LICENSE files were present
NOTE: the NOTICE file copyright still indicates 2021. This needs to be
updated to 2022, but I don't think it is significant enough to hold up
You may want to check out the Configuration Best Practices section of the
Admin Guide. Specifically, it mentions the following which will help with
the "Too many open files" issue.
Maximum File Handles
NiFi will at any one time potentially have a very large number of file
handles open. Increase
+1 (non-binding)
Performed steps in the release guide
Verified keys and checksums
Built project successfully
Installed and started out-of-the-box configuration of both NiFi and NiFi
Registry
Ran a simple flow, pushed to Registry, pulled from Registry - all
functioning normally
On Wed, Nov 3,
I am requesting assistance with three PR's, two of which have had comments
and do not have any outstanding issues currently. Unless new issues arise,
they are ready to be accepted.
NIFI-8962: Adds an 'overflow' strategy to the DistributeLoad processor
allowing an additional distribution
I'm working on NIFI-8727 [1] to fix incorrect increment/decrement of
claimant counts on content claims. The problem seems to be with cloning a
flowfile. When doing so, a new StandardRepositoryRecord is created for the
clone. See [2]. The current constructor will generate the record with a
type of
We are experiencing an issue where content claims are not being cleaned up.
This causes the content repo to grow, and eventually fill the disk. We only
see this behavior when using the RocksDBFlowFileRepository, but not when
using the WriteAheadFlowFileRepository.
Unfortunately, we have not been
Looking for a reviewer for PR #5267 (NIFI-8962). This ticket adds an
'overflow' strategy to the DistributeLoad processor.
Thanks in advance!
https://github.com/apache/nifi/pull/5267
https://issues.apache.org/jira/browse/NIFI-8962
Just run a build of current 'main' successfully. (mvn -T 3 clean install)
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /opt/maven/latest
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/opt/java/jdk-11.0.11+9
Default locale: en_US, platform encoding: UTF-8
OS
les) from a now orphaned
> connection to a now existing connection in the new version.
>
> This is the blessing and curse of operating a durable state machine
> and supporting version control changes as if the flow definition
> exists at a point in time independent of data/state flowing thro
Scenario:
Using NiFi Registry to version control changes to the graph. A development
system is used to make all changes. Once the changes are "vetted", the
production system will pull down the latest version to get the changes.
Further, the goal is to automate the version update, and not require
omparison statistics with Java
> > > > versions and component configuration details would be very helpful.
> If
> > it
> > > > is possible to run tests using a public API or deployable service,
> that
> > > > would also help confirm potential differe
processors.standard.PostHTTP/index.html
>
> Regards,
> David Handermann
>
> On Tue, Jul 27, 2021 at 9:56 AM Mark Bean wrote:
>
> > I'm strongly in favor of reducing tech debt, and moving deliberately to a
> > 2.0 release. I have a concern with just one processor that is curr
I'm strongly in favor of reducing tech debt, and moving deliberately to a
2.0 release. I have a concern with just one processor that is currently
marked as deprecated: PostHTTP. (I have not evaluated specifically any
other deprecated components; I cannot say if there are or are not similar
issues
on, Jul 19, 2021 at 4:04 PM Mark Bean wrote:
> Reviving this thread for a similar question. During the build,
> nifi-registry/nifi-registry-core/nifi-registry-web-ui attempts another wget
> command.
>
> [ERROR] gyp http GET
> https://nodejs.org/download/release/v10.16.3/
(for example.) No problems there. However,
this same methodology does not seem to work for the required
node-v10.16.3-headers.tar.gz file.
Is there a similar maven switch to use to locate the node headers file?
Thanks,
Mark
On Fri, Jul 16, 2021 at 12:29 PM Mark Bean wrote:
> Thanks for the feedback M
+1 (non-binding)
I'm all in favor of NiFi Registry being part of the NiFi codebase. However,
I'm discovering some build issues specific to nifi-registry when building
on a private network. I consider this just growing pains, and fully support
the overall concept and associated advantages!
-Mark
ted on-demand, I'm not opposed to making the
> profile inactive by default, but would like to get others' thoughts on
> this as well. We would want to update any READMEs, Dev guides, etc. if
> we disable by default any profiles that used to be enabled.
>
> Regards,
> Matt
>
addition to documenting usage
> of the REST API, it offers interactivity. If you’ve never seen Swagger UI
> before, can see a demo of it here [2]. It is completely data driven by a
> swagger.json spec, so in Registry it dynamically generates our REST API
> endpoints.
> >
> >
perty to location
> - Do what we do now, but detect if the tarball is not reachable via the
> network and gracefully continue the build without that piece
>
> > On Jul 15, 2021, at 3:23 PM, Mark Bean wrote:
> >
> > Thanks. That profile is what I needed to get beyond
-registry-web-api/pom.xml#L136
> >
>
> Kevin
>
> > On Jul 15, 2021, at 1:54 PM, Mark Bean wrote:
> >
> > I'm trying to build rel/nifi-1.14.0 on a private, non-Internet connected
> > network. The nifi-registry portion is failing.
> >
> > [ERROR] Failed to
I'm trying to build rel/nifi-1.14.0 on a private, non-Internet connected
network. The nifi-registry portion is failing.
[ERROR] Failed to execute goal
com.googlecode.maven-download-plugin:download-maven-plugin:1.2.1:wget
(download-swagger-ui) on project nifi-registry-web-api: IO Error: Error
+1 (non-binding)
Checked out tag nifi-1.14.0-RC2, confirmed commit hash
Built from source code using contrib-check profile
Linux, Java 8, Maven 3.8.1
MacOS, Java 11, Maven 3.6.3
Installed secure 2-node cluster using embedded Zookeeper (ZK not secured
with TLS)
Installed nifi-registry
Ran
; > On Tue, Jul 6, 2021 at 8:21 AM Joe Witt > > joe.w...@gmail.com>> wrote:
> > > >
> > > > Team
> > > >
> > > > Going to try to pull the rc together today. Havent looked at what
> > remains
> > > but it is time. Will
lace to do this is
though.
Would this be in the StandardRemoteGroupPort? Or maybe within the transaction
itself (AbstractTransaction)? I want to avoid constantly recreating a
connection when not required since that could cause a performance impact.
Thanks,
Mark
On 2021/07/08 18:04:14, Mark B
We're seeing some odd behavior using site-to-site. The input port on a
3-node cluster will eventually stop receiving new data. In the log, I see
the following:
2021-07-08 13:13:14,010 ERROR [NiFi Web Server-43017]
o.a.nifi.web.api.ApplicationResource Exception detail:
And, for clarification, when a PG is imported from NiFi Registry, the
initial state of non-disabled components is 'STOPPED'. It takes user
interaction to put the components into a running state.
Agree with Andrew to disable (in the versioned flow in the Registry) any
component which you do not
1 at 11:26 AM Chris Sampson
> > > wrote:
> > > >
> > > > FYI, there's a new thread in slack about the new
> single-user-authoriser
> > > > setup - user has https but no users/policy screen for setting up
> AuthZ.
> > > >
> > > > Might be wor
Raghu,
Images do not come through on the email list. If possible, please provide a
link to a publicly accessible location where you can place the image.
Have you reviewed the log files, particularly nifi-bootstrap.log and
nifi-app.log? Please provide any errors from these files.
Thanks,
Mark
There are three open PR's I would appreciate some eyes on before the RC
process is kicked off. Two of the three have been reviewed, but not yet by
a committer.
https://github.com/apache/nifi/pull/5094
https://github.com/apache/nifi/pull/5061
https://github.com/apache/nifi/pull/5064
Thanks in
In addition to Mark Payne's suggestion - which you can run and evaluate
locally, just not upload results - you can also look at several aspects of
ZooKeeper. Firstly, are you running embedded or external ZooKeeper? We have
found that external is far more reliable especially for "busy" clusters.
The lack of "Version" on the context menu implies the Registry has not been
added to your NiFi. Have you added the running NiFi Registry as a client to
your NiFi instance? To do so, go to the Global Menu (upper right), choose
Controller Settings, and select the Registry Clients tab. Add your
I'm excited for the next release too. In addition to some of the more
obvious features, there are two PR's looking for some attention.
https://github.com/apache/nifi/pull/5094
https://github.com/apache/nifi/pull/5061
Thanks!
-Mark
On Thu, May 27, 2021 at 4:20 PM Chad Zobrisky wrote:
> +1 on
Congrats Chris! Thanks for your continued support.
-Mark
On Thu, May 13, 2021 at 4:25 PM Joe Witt wrote:
> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Chris has accepted the PMC's invitation to become a committer on the
> Apache NiFi project. We greatly appreciate
There is a PR [1] with a failed workflow job. It looks like it timed out,
but that there may not have been anything inherently wrong with it.
Can a task be resubmitted?
[1] https://github.com/apache/nifi/pull/5061
Thanks,
Mark
Another approach would be to have a time-based build, say no more
frequently than once/day. You would lose granularity to a specific commit,
but reduce compute cycles required by reducing the number of builds being
executed.
Just a thought.
On Mon, Apr 19, 2021 at 2:34 PM David Handermann
I like the idea of a marketplace and a reduced footprint for the NiFi
application. One of the things to consider in the implementation is how a
user gets information on components which are not installed, but are
available in the marketplace. This is not only a matter of version, but
also
Congrats Otto!
-Mark
On Mon, Mar 22, 2021 at 2:28 PM Peter Wicks (pwicks)
wrote:
> Micron Confidential
>
> Congratulations Otto!
>
> From: Joe Witt
> Date: Monday, March 22, 2021 at 12:16 PM
> To: dev@nifi.apache.org
> Subject: [EXT] [ANNOUNCE] New Apache NiFi Committer Otto Fowler
>
-1 (non-binding)
In a flow from 1.13.1, UpdateAttribute processor contained rules in the
Advanced UI. Installed 1.13.2-RC1. Placed 1.13.1 flow.xml.gz into the new
1.13.2-RC1 conf/ directory; started NiFi.
The rules in the Advanced UI could not be loaded. UI reports "Unable to
load the rule list
I'd like to discuss migrating to Java 11 as the minimum required Java
version for NiFi. We've been supporting both Java 8 and Java 11 for some
time now. There is increased overhead in verifying builds with two
different versions. There are some features and syntax available in Java 11
which cannot
+1 (non-binding)
Verified signature and checksums
Downloaded source and built with Java 8 and Java 11
MacOS, 11.2.3
Java 11.0.9, x86_64
Java 1.8.0_282, x86_64
Maven 3.6.3
Verified README, NOTICE and LICENSE
Ran in both Java 8 and Java 11 JVM with a _very_ basic flow. All basic
functions
obably at least 1.11.0
>
> Thanks
> -Mark
>
> Sent from my iPhone
>
> > On Mar 4, 2021, at 1:50 PM, Mark Bean wrote:
> >
> > A user has reported a problem with load balancing. Frequently, the UI
> will
> > show files in the connection which is configured fo
A user has reported a problem with load balancing. Frequently, the UI will
show files in the connection which is configured for 'round robin' load
balancing. The number for flowfiles has reached the backpressure limit.
However, a 'list queue' indicates there are no flowfiles. Additionally, the
+1 (non-binding)
Verified signature and checksums
Downloaded source and built with Java 8 and Java 11
mvn -T 1C clean install -Pcontrib-check,include-grpc
MacOS, 10.15.7
Java 11.0.9, x86_64
Java 1.8.0_282, x86_64
Maven 3.6.3
Verified README, NOTICE and LICENSE
Ran in both Java 8 and
+1 (non-binding)
Verified signature and checksums
Downloaded source and built with Java 8 and Java 11
mvn -T 1C clean install -Pcontrib-check,include-grpc
MacOS, 10.15.7
Java 11.0.9, x86_64
Java 1.8.0_282, x86_64
Maven 3.6.3
Verified README, NOTICE and LICENSE (noting 2020 date in
Sorry.. wish I had caught it in RC1, but stopped short since RC2 became
inevitable.
Happy New Year
On Tue, Feb 2, 2021 at 7:19 PM Joe Witt wrote:
> meh yeah we should fix. id not sink the rc over it but ill fix
>
> thanks
>
> On Tue, Feb 2, 2021 at 5:16 PM Mark Bean wrot
I hate to be trivial, but the NOTICE file included in 1.13.0-RC2 includes
the following header:
Apache NiFi
Copyright 2014-2020 The Apache Software Foundation
Is it an issue that it states 2020 instead of 2021?
Asking out-of-band from the voting thread.
Thanks,
Mark
Today, I also noticed that the following modules still have code in them.
However, they are not listed as a module in the corresponding pom.xml.
nifi-docker/docker-compose
nifi-docker/dockermaven-stateless
nifi-framework-bundle/nifi-framework/nifi-stateless
Is this dead code that should simply
Committers,
I just submitted a trivial PR - literally a one-line change to fix a UI
problem. Any chance this could get into the upcoming 1.13.0-RC2?
https://github.com/apache/nifi/pull/4794
Thanks,
Mark
; > > >> I have https://github.com/apache/nifi/pull/4632 which fixes an OOME
> > in
> > > >> PutAzureBlobStorage reported in
> > > >>
> > >
> >
> https://lists.apache.org/x/thread.html/rdef82be24828277b85bdc94dc57a8fb9df6f73552dae
't one of those. I don't care what's coming
> through, I just want to get every flowfile straight through with no
> changes.
>
> Thanks.
>
> Russ
>
> On 1/9/21 9:09 AM, Mark Bean wrote:
> > Russell,
> >
> > You can use "session.get(N)" where N is a
Russell,
You can use "session.get(N)" where N is an integer. This will get up to N
flowfiles per OnTrigger() call.
-Mark
On Fri, Jan 8, 2021 at 5:07 PM Russell Bateman
wrote:
> Very well, I have decided to force customer flowfiles through this
> processor (I did check out the /Listen/*
all the versioned PGs happens in the background
> as the nifi server itself, so it needs read access to all buckets.
>
> On Wed, Jan 6, 2021 at 9:22 AM Mark Bean wrote:
> >
> > I created a new bucket in NiFi Registry without making it publicly
> visible.
> > Then, I a
I created a new bucket in NiFi Registry without making it publicly visible.
Then, I added myself to the policies on the bucket with Read, Write and
Delete permissions; I did not add the Apache NiFi server to the policies.
In Apache NiFi, I added a flow to the Registry. I could also pull this flow
1 - 100 of 247 matches
Mail list logo
