Re: new PackageFlowFile processor

Most of the complexity in MergeContent is around the bundling parameters... this processor would do no bundling, just straight pass through to the packaging library. No worries for the user about setting max package size, number of entries, number of bins, bin age, headers, footers, etc... even

Re: new PackageFlowFile processor

I have had to use that pattern myself recently. I think a simple PackageFlowFile processor makes a lot of sense. I am +1. Brandon From: Michael Moser Sent: Friday, September 8, 2023 9:52:52 AM To: dev@nifi.apache.org Subject: new PackageFlowFile processor

Re: [discuss] nifi 2.0 and Java 21…

+1 to requiring java 21. Starting off as "up to date" as possibly makes a lot of sense, and some of the new features seem especially relevant to NiFi. I definitely understand the concerns about organizations being willing / able to approve Java 21... But those same organizations might also be

Re: NiFi 2.0 - QuestDB

I also agree... I've been doing some testing recently, and not having to note relevant stats before a config change and restart is a huge improvement. From: Pierre Villard Sent: Wednesday, July 19, 2023 8:54:13 AM To: dev@nifi.apache.org Subject: Re: NiFi 2.0 -

Re: [DISCUSS] rename master branch, look through code for other related issues

"Instead of banning every word out there, we should make the mental effort to do better than the political correctness movement that stops at the surface." I think this is a pretty clear false dichotomy. Doing one doesn't preclude the other. The statement above goes on: "So, let’s call it

Re: [EXT] Re: [VOTE] Create NiFi Standard Libraries sub-project

+1, binding Brandon From: Mark Payne Sent: Wednesday, September 4, 2019 1:35 PM To: dev@nifi.apache.org Subject: Re: [EXT] Re: [VOTE] Create NiFi Standard Libraries sub-project I'm a +1 as well. Thanks -Mark > On Sep 4, 2019, at 6:02 AM, Pierre Villard >

Re: [EXT] [discuss] Splitting NiFi framework and extension repos and releases

In regards to "We 'could' also split out the 'nifi-api'...", NiFi 2.0 would also be a good time to look at more clearly defining the separation between the UI and the framework. Where nifi-api is the contract between the extensions and the framework, the NiFi Rest api is the contract between the

Re: Dark mode

I think there are a lot of people that would be a big +1 on this. Maybe even more so if it was abstracted so there could be multiple / custom "themes" (e.g. dark, classic, high contrast / 508 compliant...). Brandon On Fri, Jul 13, 2018 at 7:29 AM Joe Witt wrote: > Rich > > This could

Re: [discuss] should we do a nifi 1.7.1 release?

This one may be worth fixing in 1.7.1 as well: https://issues.apache.org/jira/browse/NIFI-5331 On Thu, Jul 5, 2018 at 12:23 PM Joe Witt wrote: > team, > > Wanted to kick off a thread to suggest we do a nifi 1.7.1 release. It > sounds like we might have an issue handling wildcard certs in

Re: NiFi (UNCLASSIFIED)

Justin, The 4.x version you're referencing is specific to the organization you work for. I would direct questions specific to this version to your organization's internal chatrooms / DLs. If you need further guidance, please let me know. Brandon On Tue, Jun 26, 2018 at 3:49 PM Cetron, Justin

Re: [EXT] Re: Primary Only Content Migration

In this particular case, the easiest thing to do may be to keep track of the hostname of the original node of the file (before split and distribution). Then, just send all of the pieces back to the originator node when done, and merge there. It would be nice to have automatic queue balancing of

Re: JSON Path Expression

I happened to be playing with this Friday... You can try single quotes in the jsonPath as well. Brandon On Fri, Apr 27, 2018 at 5:05 PM Otto Fowler wrote: > $.fields[?(@.name==Type)].maskType > > > no \” \” > > When JsonPath evaluates the path against the content, the

Re: Is there a configuration to limit the size of nifi's flowfile repository

All, This is something I think we shouldn't dismiss so easily. While the FlowFile repo is lighter than the content repo, allowing it to grow too large can cause major problems. Specifically, an "overgrown" FlowFile repo may prevent a NiFi instance from coming back up after a restart due to the

Re: Empty String in UpdateAttribute

Joe, Primarily, I believe the use case is legacy flows pre-dating the existence of "delete attribute" functionality. The most "correct" solution may be to delete the attribute, but that doesn't mean we should break backwards compatibility. Brandon On Fri, Jan 19, 2018 at 5:33 PM Joe Percivall

Re: PRC_NIFI_Pricing_Service - Build # 6 - Fixed!

sweet! On Fri, Jan 19, 2018 at 2:46 PM Michael Moser wrote: > Somebody's Jenkins is spamming everyone who has made a commit recently! > > > -- Forwarded message -- > From: > Date: Fri, Jan 19, 2018 at 11:23 AM > Subject:

Re: [DISCUSS] Apache NiFi distribution has grown too large

I agree... Long term extension registry, short term one repo with different assemblies (e.g. standard, slim, analytic, etc...). Brandon On Sat, Jan 13, 2018 at 1:35 PM Pierre Villard wrote: > Option #3 also has my preference. But it's probably a good idea to only >

Re: [CANCEL] [VOTE] Release Apache NiFi 1.4.0

Jeff, Any updates on RC2? Brandon On Mon, Sep 25, 2017 at 4:56 PM Jeff wrote: > Mark, > > I also would like to get RC2 out as soon as possible, but due to time > constraints on other tasks, I will not be able to create RC2 until tomorrow > afternoon. However, with a

Re: [EXT] Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?

es that will go in 1.4.0 release? > > Thanks!! > > On Wed, Sep 20, 2017 at 9:53 AM, Brandon DeVries <b...@jhu.edu> wrote: > > > All, > > > > I think we should plan on calling for a vote on Friday. That gives two > > days to wrap up any outs

Re: [EXT] Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?

gt; >> > being committed > >> to > >> > post 1.4.0. Thoughts? > >> > > >> > On Mon, Sep 18, 2017 at 2:50 PM Joe Witt <joe.w...@gmail.com> wrote: > >> > > >> > > Definitely agree with Brandon that due for a 1.4.0 and it has som

Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?

eatures worked on and ready to go, by all > means, let's have 1.4.0. But if 1.4.0 is little more than 1.3.1, let's > rethink why we'd do that. > > Russ > > > On 09/18/2017 12:08 PM, Brandon DeVries wrote: > > +1, it seems like we're do for a release. It's been a week, a

Re: RTC clarification

There are always exceptions, but I think the best way to ensure that the spirit of what we're going for is being followed is to say "no one commits their own code". While additional eyes are never going to be a bad thing, requiring a second person to "sign off" on and then commit the code would

Re: Closing in on a NiFi 0.8.0 release?

lled out are things which > > impact licensing only (specifically the no longer allowed cat-x json > > library). I would be far more comfortable with 0.7.3 release which > > would be fixing whatever bugs have been addressed. That avoids the > > concern I noted above for this c

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Fri, Feb 10, 2017 at 6:36 PM Andre wrote: > +1 binding > > On Sat, Feb 11, 2017 at 3:40 AM, Bryan Bende wrote: > > > All, > > > > Following a solid discussion for the past few days [1] regarding the > > establishment of Registry as a

Re: [DISCUSS] Run Once scheduling

I think answering Joe's question is step one. However, I was curious and tried something: public void onTrigger(...){ if(!isSheduled()){ return; } FlowFile flowFile = session.get() if (flowFile == null){ return; } session.transfer(flowFile, REL_SUCCESS);

Re: OCSP validation not happening for cluster servers

Matt, I think the issue isn't going through the REST api. It's that nodes of a cluster can connect to the cluster, whether or not their certificate has been revoked. In other words, not a rogue random client, but a rouge nifi node... Brandon On Mon, Dec 19, 2016 at 11:22 AM Matt Gilman

Provenance repo corruption

Devs, I just opened a ticket to address an issue we've encountered with Provenance repo corruption[1]. This would address (as is currently partially being done) how to recover from a corrupt provenance repo. However, the question is whether we can avoid this sort of corruption in the first

Re: [DISCUSS] Closing in on a 0.x release

I agree sooner rather than later for cutting 0.7.1. I think Mike's question to some degree was whether or not some of those tickets were worth fixing in 0.x. For example, I'm not sure how much I care about: NIFI-2571 deprecate NiFiProperties.getInstance() NIFI-2163 nifi.sh follow the Linux

Re: [VOTE] Release Apache NiFi 0.7.0 (RC1)

In that case, I'd like to request the vote be extended to Tuesday afternoon. There is at least one critical bug fix that just got in that we haven't been able to test. We've only been able to reliably replicate the problem on one system, and I do not have access to it over the weekend. It is not

Re: [DISCUSS] Extraction of Extension API

+1. Seems like a good idea, and now is a good time. Brandon On Fri, May 6, 2016 at 3:31 PM Aldrin Piri wrote: > All, > > I would like to propose a refactoring of the nifi-api for our master/1.0 > branch. In summary, a lightweight and concise view of this module allows >

Re: [DISCUSS] Removal of FlowFilePrioritizer as first-class extension point

+1. This seems like something we should provide options for (as we do), but doesn't really need to be made / kept accessible for extension. Brandon On Fri, May 6, 2016 at 11:45 AM Mark Payne wrote: > I'm definitely a +1. In my experience, the way that most people think >

Re: [discuss] PropertyDescriptor name and displayName attributes

d flexibility in > displayed name while retaining configuration sanity - is a win. > > Thanks > Joe > > On Fri, May 6, 2016 at 10:45 AM, Brandon DeVries <b...@jhu.edu> wrote: > > I guess my only objection is, do we really need Option 2? If all you > want > > to do

Re: [discuss] PropertyDescriptor name and displayName attributes

agree this discussion > > ended up getting us to a great place though as we should all strive to > > support internationalization. > > > > With an approach like this I am onboard. I think this balances our > > goals of having a simple to use API but also all

Re: [discuss] PropertyDescriptor name and displayName attributes

ith an approach like this I am onboard. I think this balances our > goals of having a simple to use API but also allows those who want to > support multiple locales to do so cleanly. > > Thanks > Joe > > [1] https://docs.oracle.com/javase/tutorial/i18n/resbundle/propfile.html > >

Re: [discuss] PropertyDescriptor name and displayName attributes

need someone to explain how internationalization would be > implemented, and how setting the displayName helps. > What Brandon described makes sense to me because it is something outside > the Java code, which is different then saying all PropertyDescriptor > instances need name and d

Re: Apache Nifi Vs Spring XD, which one is better

All, It seems like we get this sort of question a lot, and Simon's answer here was really good. We've had similar for discussions for Kafka[1], Storm and Spark[2]. Should we think about adding a comparison to other technologies / applications to the FAQ? Not in a sales sheet sort of way, but in

Re: [discuss] PropertyDescriptor name and displayName attributes

+1. I think being able to move the displayName out of code an into config / ResourceBundle will make it much easier to support i18n[1]. If no config is provided, the name is the default... otherwise, the name displayed is determined by the locale. Updating the mock framework to complain about

Re: [VOTE] Establish Apache MiNiFi, a subproject of Apache NIFi

+1 On Sat, Apr 9, 2016 at 8:17 AM Mark Payne wrote: > +1 > > Sent from my iPhone > > > On Apr 9, 2016, at 7:51 AM, Matt Gilman wrote: > > > > +1 > > > > Sent from my iPhone > > > >> On Apr 9, 2016, at 1:13 AM, Joe Witt wrote: >

Re: [DISCUSS] git branching model

I agree with Tony on option 1. I think it makes sense for master to be the most "advanced" branch. New features will then always be applied to master, and optionally to other branches for older version support as applicable / desired. On Tue, Mar 29, 2016 at 10:16 AM Tony Kurc

Re: [DISCUSS] NiFi 0.5.1 release

+1 for getting 0.5.1 out the door sooner rather than later. Like you said... if the other tickets get sorted out in a week or so, we can do 0.5.2. Otherwise, 0.6.0 isn't that far off. But a fix involving data loss is worth doing quickly. Brandon On Fri, Feb 19, 2016 at 4:18 PM Joe Witt

Re: How to dynamically update URL in GetHTTP processor ?

Shweta, Take a look at InvokeHTTP[1] instead of GetHTTP. InvokeHTTP allows Expression Language in the URL, so you can specify the page number. Let us know if you have any other questions. Thanks. [1]

Re: Questions about the ordering of the FlowFile.

Paresh, You might want to look at the PriorityAttributePrioritizer[1]: *PriorityAttributePrioritizer*: Given two FlowFiles that both have a "priority" attribute, the one that has the highest priority value will be prprocessed first. Note that an UpdateAttribute processor should be used to

Re: [VOTE] Release Apache NiFi 0.3.0

To copy and paste from Mark: Downloaded source, verified checksums and that the key/signature was valid. Was able to build with contrib-check without any problems. README/LICENSE/NOTICE all look good. Application runs without any problems. +1 (binding) - Release this package as nifi-0.3.0

Re: 0.3.0 release

e, I'd > ask that you consider a ticket I just created: > https://issues.apache.org/jira/browse/NIFI-938 > > Thanks, > Brian > > On Tue, Sep 8, 2015 at 3:05 PM, Brandon DeVries <b...@jhu.edu> wrote: > > > All, > > > > It looks like there's only one t

Re: [DISCUSS] Feature proposal: Read-only mode as default

I think undo is the most important part here. I agree with Alex's statement, accidents happen; I prefer to enable users to learn from mistakes and exercise more care next time. Delete confirmations may be fine (although I suspect they would begin to annoy me fairly quickly... if it's just for

Re: Help required with my custom controller service

All, Was this ever solved / explained? I'm having a similar issue. If there's a simple answer that I'm missing that would be great... otherwise I might post an example set of NARs somewhere tomorrow. Probably the simplest question first is, if I want to create a custom processor that uses a