Re: Request for review - NIFI-5573

y with you over on GitHub. > > Cheers, > Kevin > > > On Jun 16, 2021, at 10:56, Lars Francke wrote: > > > > Hi everyone, > > > > I've opened a PR for NIFI-5573[1] in 2018 and never had time to > incorporate > > review feedback (it's tiny). I actual

Request for review - NIFI-5573

Hi everyone, I've opened a PR for NIFI-5573[1] in 2018 and never had time to incorporate review feedback (it's tiny). I actually closed it earlier this year but it turns out I still want the change so I just brought it up to date. If anyone has time to look at my Pull Request that'd be greatly

Re: [DISCUSS] On HBase client retries (NIFI-6197)

ase can implicitly ride > over a transient/automatically-recoverable state". > > [1] https://github.com/apache/nifi/pull/3425#issuecomment-487962996 > > On 2/19/20 11:14 AM, Lars Francke wrote: > > That's what I suggested[1] and Bryan rejected[2] > > > > [1]

Re: [DISCUSS] On HBase client retries (NIFI-6197)

be instead of requiring an implicit way to do this (requiring NiFi > >> code changes), we could solve the problem at the "human level": create > >> docs that walk people through how to push a dummy record through the > >> service/processor with the low config

Re: Latest NiFi customs?

Hi, I have just one data point on the version but I would suggest moving to 1.9 if you're just starting out and if you're using the Record based processors with potentially dynamic/changing schemas. The automatic schema inference described in this blog post[1] makes things much easier (or

Re: Code style & backwards compatiblity

processors that you were thinking of? > > On Fri, Apr 5, 2019 at 11:33 AM Lars Francke > wrote: > > > > Hi, > > > > looking at Processors I often see things (e.g. internal state) are > > protected, public or package private that really shouldn't/needn't be.

Re: Stability of RecordReader et. al.

se statements, but maybe others have different > thoughts. > > -Bryan > > On Fri, Apr 5, 2019 at 11:21 AM Lars Francke > wrote: > > > > Hi, > > > > a customer stumbled upon these comments in RecordSetWriterFactory, > > RecordReader, WriteResult and

Code style & backwards compatiblity

Hi, looking at Processors I often see things (e.g. internal state) are protected, public or package private that really shouldn't/needn't be. A few years ago I tried to change one of those and was told that others might rely upon and I can't change it for backwards compatibility reasons. I've

Stability of RecordReader et. al.

Hi, a customer stumbled upon these comments in RecordSetWriterFactory, RecordReader, WriteResult and RecordSetWriter: "PLEASE NOTE: This interface is still considered 'unstable' and may change in a non-backward-compatible manner between minor or incremental releases of NiFi." Is this still

Re: [DISCUSS] Deprecate processors who have Record oriented counterpart?

I'm also against deprecation. Sometimes it's nice to throw a quick workflow together where I don't care about schemas at all. On Sat, Feb 23, 2019, 18:06 Ryan Hendrickson < ryan.andrew.hendrick...@gmail.com> wrote: > We often don't use the Record Processors because of the Schema requirement

Re: API to get all Policies

the > Rest API documentation are accurate. If you have any questions on that let > me know. Happy to help review a PR if you submit one. > > Regards, > Kevin > > On 11/9/18, 06:23, "Lars Francke" wrote: > > I've just tried implementing my new reso

Re: API to get all Policies

. But that seems overly complicated. So if you don't object I'd create a Jira. Cheers, Lars On Fri, Nov 9, 2018 at 10:01 AM Lars Francke wrote: > Andy, > > that's a good question. I have to admit that I thought about it and then > saw that there is already an Authorizable for this s

Re: API to get all Policies

resto.apa...@gmail.com > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > On Nov 9, 2018, at 3:31 AM, Lars Francke wrote: > > > > Hi, > > > > I was tasked with writing a tool to generate a kind of "audit report". > For >

API to get all Policies

Hi, I was tasked with writing a tool to generate a kind of "audit report". For that I need to get all policies that people have across various systems. NiFi is one of them. I see that we have a REST API for Policies but that doesn't expose a method to expose _all_ policies. I'd like to add a

Re: Question about nifi-env.sh

I've opened NIFI-5573 (<https://issues.apache.org/jira/browse/NIFI-5573>) for this On Mon, Aug 27, 2018 at 12:38 PM, Lars Francke wrote: > Peter, > > thanks for the comments. > It seems as if Joe and you are in agreement. > I'd be in favor of changing it to the way Ha

Re: Question about nifi-env.sh

trivial. Any hints are highly appreciated. [1] <https://issues.apache.org/jira/browse/NIFI-5352> & < https://issues.apache.org/jira/browse/NIFI-5350] On Fri, Aug 24, 2018 at 4:30 PM, Lars Francke wrote: > Thanks for the quick response Joe. > > Yes, I assumed as much that's w

Re: Question about nifi-env.sh

l/discussing it - need folks like mark payne > and yolanda davis and others who wrote some of those bits to comment. > I say this because these scripts/start routines are super heavily used > for deployment processes that I know a lot of users depend on. > > Thanks > > On Fri, Aug

Question about nifi-env.sh

Hi, I'm trying to use the environment variables NIFI_PID_DIR and NIFI_LOG_DIR to change those directories. Unfortunately nifi-env.sh is being called by nifi.sh which overrides them without any way to override them. To make it even more confusing the path for NIFI_PID_DIR is different than the

Re: Request for Reviews NIFI-5352 & NIFI-5350

Hi everyone, just bumping this again. I'd love a review for NIFI-5350: < https://issues.apache.org/jira/browse/NIFI-5350> & < https://github.com/apache/nifi/pull/2823> Thank you! Lars On Wed, Jul 11, 2018 at 9:09 AM, Lars Francke wrote: > Thank you James for taking a

Re: Request for Reviews NIFI-5352 & NIFI-5350

Thank you James for taking a look at one of them! I'd be very grateful for a volunteer for NIFI-5350 On Tue, Jul 10, 2018 at 8:54 PM, Lars Francke wrote: > Hi everyone, > > can I interest anyone in taking a look at two JIRAs I created a few days > back: > > <https://i

Request for Reviews NIFI-5352 & NIFI-5350

Hi everyone, can I interest anyone in taking a look at two JIRAs I created a few days back: & < https://github.com/apache/nifi/pull/2823> & < https://github.com/apache/nifi/pull/2825> It's three

Re: Github mails

Which ones are you referring to? > > > > > > Thanks > > > Joe > > > On Jun 27, 2016 11:45 AM, "Andy LoPresto" <alopre...@apache.org> > wrote: > > > > > > > +1. > > > > > > > > Andy LoPresto > >

Re: FlowFiles missing (MissingFlowFileException)

like then rather than > > emailing he decided to go get coffee :-). > > > > We will be working this up for very prompt resolution and it warrants > > a release in my view. > > > > Can you confirm that you are either not using archiving or you are > > using it

Re: FlowFiles missing (MissingFlowFileException)

e.w...@gmail.com> wrote: > Interesting. What that suggests is the content has been removed from > the content repo itself. > > Thanks > Joe > > On Tue, Feb 16, 2016 at 4:15 PM, Lars Francke <lars.fran...@gmail.com> > wrote: > > I attached a debugger and ch

FlowFiles missing (MissingFlowFileException)

Hi, I'm trying to understand what happened and how I can prevent this in the future. The outcome seems to be that all my FlowFiles which were sitting in a connection have been deleted from disk. I had a flow with two processors connected via a single connection. What I did: * Stop all

Re: [VOTE] Release Apache NiFi 0.5.0 (RC3)

+1 (non-binding) Builds okay and ran some basic flows including some basic testing of the state management On Sat, Feb 13, 2016 at 12:27 AM, Tony Kurc wrote: > Hello > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-0.5.0. > > The source zip,

Re: [DISCUSS] Apache NiFi 0.5.0 RC1

Hi Tony, maybe I missed it in the Repo but did you also provide binaries to test? I'll try building it myself now (as you ask) but wanted to check anyway. Cheers, Lars On Sun, Feb 7, 2016 at 1:34 AM, Tony Kurc wrote: > Hello > We put together the RC1 for nifi-0.5.0. Because