[Discussion] JSON Schema support for Records

Team, I would like to offer the following proposal for discussion. Please share your thoughts and ideas, any input is appreciated! https://cwiki.apache.org/confluence/display/NIFI/JSON+Schema+support+for+Records Regards, Bence

Re: [DISCUSS] Validator hook for Registry events

he script and then the script >>>>> has to parse through it looking for fields to validate/check. I wonder >>>>> if we should consider defining the types of rules ourselves and >>>>> allowing some kind of rules config file to be provided. This way the &

Re: [DISCUSS] Validator hook for Registry events

;> >>> As a side-note, another improvement could be to prevent a flow from being >>> versioned in the registry if a required rule is violated (I'm talking >> about >>> the new feature coming with NiFi 2.0). Just a thought for an additional >>>

[DISCUSS] Validator hook for Registry events

Hi, I recently found the need for custom validation to maintain NiFi Registry content. This includes checks such as enforcing naming conventions when creating a Bucket and similar usage specific cases. While exploring the Registry's codebase, I came across the EventHookProvider, which aligns wi

Property management - reducing duplication

Hi Team, I was touching some test related code in the other day and it brought to my attention how much partly duplicated nifi.properties files we do have in the project in various places. While I was searching for the value of a given property in these files, it got me thinking that when a pr

Re: NiFi 2.0 - QuestDB

ile instead of failing to start. If we go > forward with QuestDB as the default strategy for status history, we should > build in the resilient approach as a prerequisite to enabling it in the > default configuration. > > Regards, > David Handermann > > On Wed, Jul 19,

Re: NiFi 2.0 - QuestDB

start is a >> great improvement for NiFi troubleshooting. It also gives the ability to >> store this information for a longer period of time. I'm definitely in favor >> of making this the default starting with NiFi 2.0. >> >> Le mer. 19 juil. 2023 à 13:49, Simon

NiFi 2.0 - QuestDB

Hi Community, I was thinking if it would make sense to set the QuestDB as default for status history backend in 2.0? It is there for a while and I would consider it as a step forward so the new major version might be a good time for the wider audience. It comes with less memory usage for bigger

Re: [Need help] Set up Apache Nifi and get error

Just to be sure, not to loose any data: before doing any tempering with the flow.xml.gz, please back up everything (original flow.xml.gz from 1.16.2, etc.) > On 2023. Feb 21., at 9:02, Simon Bence wrote: > > Hi Tuyen, > > The attached error message contains the following lines:

Re: [Need help] Set up Apache Nifi and get error

Hi Tuyen, The attached error message contains the following lines: Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Invalid byte 1 of 1-byte UTF-8 sequence. This could be the sign of a misformatted XML. Is it possible that the XML was edited by hand? Pleas

Re: [VOTE] Adopt NiFi 2.0 Proposed Release Goals

+1 (non-binding) > On 2022. Dec 12., at 18:02, David Handermann > 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 2.0: > > 1. Remove Java 8

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

+1 (non-binding) I went through the normal steps. I also started and executed some basic scenarios about the recent registry related changes. Build on macOS Catalina 10.15.7 Maven: 3.6.3 Java version: 11.0.15, vendor: Azul Systems, Inc. Default locale: en_GB, platform encoding: UTF-8 OS name: "

Re: [VOTE] Release Apache NiFi 1.17.0 (rc1)

Hi! +1 (non-binding) I went though the release testing steps and also tested NIFI-9615 and NIFI-9776 against the major cases from the original tickets. LGTM. macOS Catalina 10.15.7 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) OpenJDK Runtime Environment Zulu11.56+19-CA (build 1

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.3.5

+1 (non-binding) Thanks for the fix! I went through the helping guide and everything looked fine to me. Regards, Bence > On 2022. Jul 20., at 22:37, Bryan Bende wrote: > > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache > NiFi NAR Maven

Re: Custom Processor Query

Hi Muhammad, I am not sure what scenario you intend to cover, but in many cases, the “scripted” processor family is a satisfying solution to work with Python. I suggest you to take a look of the InvokeScriptedProcessor and the ScriptedTransformRecord. Depending on your needs, they might help yo

Re: [discuss] 1.12.0 or 1.11.5...

Hi, If the community decides to go on with 1.11.5, I kindly ask to include NIFI-7292 in order to fix the issue reported in NIFI-7454. Thank you! https://issues.apache.org/jira/browse/NIFI-7454 https://issues.apache.org/jira/browse/NIFI-7292

Re: [DISCUSS] Advanced search capabilities

at was fixed in 1.11. The ExecuteGraphQuery processor >>> will >>>>> allow you to execute Cypher or Gremlin commands/scripts depending on >>>> which >>>>> controller service/driver you configure. >>>>> >>>>> On Fri, Feb 21

Re: [DISCUSS] Advanced search capabilities

ql-e3fa484de2ea >>> From the idea it could go in this direction - of course much more >>> rudimentary. Then one would have the possibility to have only the results >>> displayed as text or to find out exploratory connections (graph layout). >>> The built-in data li

[DISCUSS] Advanced search capabilities

Dear Community, In my project, I do use relatively high number of processors and process groups. The current search function on the NiFi UI has no capabilitites to narrow the results based on the group, which would make the results more relevant, so I would like to propose a possible solution. Pl