Re: "External" extensions

In nodejs/npm world, each module has package.json, which declaratively indicate which node version and other external modules it depends on. Similarly I am thinking Nar modules can declare which version of JVM and NiFi it depends on and also which other modules it depends on. NPM ( NiFi

RE: Next release?

Joe, This reminds me... are there any entry or exit criteria (from a defects perspective) established for NiFi releases? In other words, what is the criteria for determining when the code is ready for release and production use? Thanks Rick -Original Message- From: Joe Witt

RE: Next release?

The current process is outlined in our release guide. But the main idea is that all who wish to participate in release validation do so from the RC. Unit tests are of course run by the builds but we rely on people power to verify system level testing and that is part of that testing folks should

Re: LogAttribute - Sending that output to a custom logger?

Mark All fair points. Can you please point out which processor docs specifically should be better. Let's fix em..you will quickly lose that new user vibe and not notice what needs to improve as much. We need to make the new user experience awesome. Thanks Joe On Nov 2, 2015 10:08 AM, "Mark

Re: LogAttribute - Sending that output to a custom logger?

We greatly appreciate contributions. Your prescribed approach sounds great and if you are willing to give us a few cycles pointing out, and optionally correcting, the items that are in need of improvement, we will certainly incorporate. Thanks! On Mon, Nov 2, 2015 at 1:28 PM, Mark Petronic

Re: LogAttribute - Sending that output to a custom logger?

This thread has forked into two different conversations: 1. improvements to LogAttribute processor; 2. improvements to processor documentation. 1) re: improvements to LogAttribute - we already have NIFI-67 [1] that suggests a number of improvements to LogAttribute. One of these is the use of a

[GitHub] nifi pull request: NIFI-1051 Allowed FileSystemRepository to skip ...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/111 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: LogAttribute - Sending that output to a custom logger?

Hi Where I work we have created an attribute loggers of our own. It is a fairly simple affair which used a regex to determine which attributes to log, and writes them as key value pairs to a file, whose location is determined by a user properly. I'm happy to put this out there if anyone is

Re: Common data exchange formats and tabular data

Hello all, I am new to the NiFi community but I have a good amount of experience with ETL tools and applications that process lots of tabular data. In my experience, JSON is only useful as the common format for tabular data if it has a "flat" schema, in which case there aren't any advantages for

Re: LogAttribute - Sending that output to a custom logger?

My primary use is for understanding Nifi. I like to direct various processors output into both their logical next processor stage as well as into a log attribute processor. Then I tail the Nifi app log file and watch what happens - in real time. I do not intend to use this for long term log

Re: LogAttribute - Sending that output to a custom logger?

David, This sounds like a slightly different use case than the NiFi standard LogAttribute processor. It sounds like your processor is more of a generic attribute converter and file writer. The LogAttribute processor is designed to interact with the underlying NiFi logging subsystem, not

Re: LogAttribute - Sending that output to a custom logger?

https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide On Mon, Nov 2, 2015 at 9:04 PM, Adam Taft wrote: > David, > > This sounds like a slightly different use case than the NiFi standard > LogAttribute processor. It sounds like your processor is more of a generic