All,
I did create a ticket for this: https://issues.apache.org/jira/browse/NIFI-942
And I linked it as related to NIFI-921.
Thanks
-Mark
> From: aldrinp...@gmail.com
> Date: Wed, 9 Sep 2015 03:00:18 +
> Subject: Re: ExtractText usage
> To: users@nifi.apac
Chris,
I would venture to guess that the duplicate lines are actually the result of
the ReplaceText processor
that you are using. Regexes can be very powerful but can certainly result in a
headache. Especially
if using things like .*
This is because .* can match 0 characters, so it will match t
Mark,
That is a great idea and I can see its value when it comes to log
aggregation. What I've done is the past is use rsyslog to breakout the
separate events by type, but it can get messy very fast.
Ryan
On Wed, Sep 9, 2015 at 8:55 AM, Christopher Wilson
wrote:
> Bryan, thank you for the temp
Just wanted to make sure you all saw this:
https://news.ycombinator.com/item?id=10190846
It can add a lot of visibility to a project, especially if the maintainers jump
in to answer questions.
I believe that NiFi uses the Quartz cron syntax, which is described here:
http://quartz-scheduler.org/api/2.2.0/org/quartz/CronExpression.html
As for why, I believe it is because NiFi uses the Quartz java library to
schedule processes, so it kept with Quartz syntax rather than translating
it. I'm
Bryan, thank you for the template, I'll look through that today and see if
that will do the trick. The multi-line regex for capturing all lines
beginning with "R and ending with the next line which begins with "S" is
below.
# multi-line
# turn off greedy matches
# lookahead for lines beginning wi
Just curious - why does the NiFi cron syntax differ from crontab syntax, in
that there is a "seconds" field in NiFi cron that I don't think crontab uses?
It always throws me that there's an extra field there.
Hi Joe,
Thanks. Yes, this part is all clear. The part that makes it messier is that I
think the rejection reports are sent back by email, and that's what the data
providers are expecting. We could use PutEmail, but I just didn't know if that
was the most graceful way to do this. I'm still learni
