> Regards,
> Matt
>
> On Tue, Jul 7, 2020 at 10:14 PM Eric Secules wrote:
> >
> > Hello,
> >
> > I was wondering if there was a recommendation on how to extend the
> functionality of nifi processors without forking the nifi repository. I'm
> looking
ybe you could look to backport that change for ease? You may still need
> to look at whether the issue list is in a format you're able to use (i.e.
> it's not a parable json array).
>
>
> Cheers,
>
> Chris Sampson
>
> On Wed, 8 Jul 2020, 05:35 Eric Secules, wro
Does anyone have a suggestion for a workaround? I'm at a loss right now.
On Wed., Jul. 8, 2020, 11:11 p.m. Eric Secules, wrote:
> Hello,
>
> I believe I found a bug regarding downloading versioned process groups
> from a registry. I have logged a bug.
>
> https://issues
Looks like you are right that it is a bug. An NPE alone signals that. Now
> just needs someone to take the time to dig through it.
>
> Thanks
>
> On Thu, Jul 9, 2020 at 8:21 AM Eric Secules wrote:
>
> > Does anyone have a suggestion for a workaround? I'm at a loss righ
Hello,
I have a use case for the merge content processor where I have split the
flow in two branches (original flowfile and PDF one branch may or may not
take longer than the other) and I want to rejoin those branches using the
defragment strategy based on the flowfile UUID of the flowfile before
Sorry I should have sent this to users mailing list.
On Thu., Jul. 30, 2020, 6:13 p.m. Eric Secules, wrote:
> Hello,
>
> I have a use case for the merge content processor where I have split the
> flow in two branches (original flowfile and PDF one branch may or may not
> take
Hello,
Could you please grant contributor access to me (esecules)?
Thanks,
Eric
Hello,
I am trying to write a processor which parses an input file and emits one
JSON flowfile for each record in the input file. Currently we're calling
session.transfer() once we encounter a fragment we want to emit. But it's
not sending the new flowfiles to the next processor as it processes th
ts say. On record 51 there is a processing
> issue. What happens then?I'd also suggest this pattern generally
> results in poor performance. Can you not use the record
> reader/writers to accomplish this so you can avoid turning it into a
> bunch of tiny flowfiles?
>
> Thanks
n for reading (single session for the entire source
> file) and a different session for all the splits you'll create. But I
> might be over complicating that. MarkP could give better input.
>
> Thanks
>
> On Fri, Mar 5, 2021 at 2:18 PM Eric Secules wrote:
> >
> &g
u only have
> to process one of these files per 24 hours. But it’s worth considering.
>
> Thanks
> -Mark
>
>
>
> > On Mar 5, 2021, at 5:02 PM, Eric Secules wrote:
> >
> > Hi Joe,
> >
> > I was able to get it working by using one session to manage the
llions of FlowFiles within NiFi at a time. However, if you’re trying to
> hold a million FlowFiles in heap, you’re going to use a huge amount of
> heap. This is predominantly due to the HashMap that is used to store
> attributes. Those can quickly use up a huge amount of heap.
>
> Thanks
&g
trying to hold a million FlowFiles in heap, you’re going
>> to use a huge amount of heap. This is predominantly due to the HashMap that
>> is used to store attributes. Those can quickly use up a huge amount of heap.
>>
>> Thanks
>> -Mark
>>
>>
>> &g
First of all, this sounds like a great idea! As a user I would like a way
to find processors developed by the larger community and also contribute.
One of my concerns is the user experience around upgrading and deploying a
flow that was built with processors that have now been removed from the
bas
queues by having the ability to store at least some of the FlowFiles in the
session off-heap.
Thanks,
Eric
On Tue, Mar 9, 2021 at 10:25 AM Eric Secules wrote:
> Hi Mark,
>
> The NPE Came after trying to retrieve the parent flowfile from the
> outSession's records map. The
Hello,
I'm deploying nifi in a multitenant way, where flows pertaining to
different tenants are going to run on one nifi instance. Would it be
possible to customize the nifi logs from processors and controller services
to include the tenant id that I assign in the parameter context so that the
nif
Hello NiFi Devs,
I logged this bug not too long ago:
https://issues.apache.org/jira/browse/NIFI-10583
and I would like some validation on whether I took the right direction with
the desired behaviour being that both ProcessSessions not mutate the
flowfile passed in, rather than changing the MockP
+1 (non-binding)
Built on linux Mint:
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 17.0.8.1, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_CA, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-89-generic", arch: "amd64", family:
"u
+1 (non-binding)
- Verified signatures and hashes
- Built on M2 Macbook air
- Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /opt/homebrew/Cellar/maven/3.9.6/libexec
Java version: 11.0.21, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@11/11.0
Hi Team,
I wanted to confirm my assumption that the GET /flow/metrics/prometheus
endpoint will be the only supported prometheus endpoint in 2.0 and beyond
since the reporting task and the record sink were removed. I'm looking to
add new metrics and I'm hoping that's the only place I need to add th
Hello NiFi Devs,
I am looking for a reviewer for my bugfix for NIFI-14590
https://github.com/apache/nifi/pull/9965. The bug was that the metrics were
documented to be in milliseconds but actually were in microseconds or
nanoseconds.
Thanks,
Eric
+1 (non-binding)
Verified signature and hash.
Ran contribCheck and succeeded.
GIt tag has the right commit hash.
NIFI-14707 Uploaded hundreds of flows and it takes a lot less time and heap
use is also down from before.
My custom processors still work.
Ran my suite of flow tests.
Java 21.0.6
22 matches
Mail list logo
