Hi,
I verified the GPG signature and all hash signatures. Contrib check ran fine.
I used one of the example config.yml files in the System Admin Guide and
deployed it to the compiled binary. The tool ran successfully and wrote to a
log file on my system. I have a couple notes about the release
Github user mattyb149 closed the pull request at:
https://github.com/apache/nifi/pull/599
---
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
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/613
NIFI-2157: Add GenerateTableFetch processor
NOTE: This PR depends on #599. I put the DB-specific stuff in an interface
and used ServiceLoader to get at them, but I welcome your comments perhaps on
Hello Apache NiFi community,
Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.
# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS
# Import keys file:
gpg --import KEYS
# [optional] Clear out local
Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache NiFi
- MiNiFi,
minifi-0.0.1.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1087
The Git tag is
Have you considered using the monitorActivity processor? You can place it
after the processor to want to watch and feed it's activity lost and
activity restored relationships to the the puteEmail processor. You
configure a threshold to watch for and it can be configured to only alert
once or
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
This currently has conflicts with master and needs to be rebased before it
can be merged (sorry for taking so long to review the PR).
---
If your project is set up for it, you can reply to this
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69829659
--- Diff:
nifi-api/src/main/java/org/apache/nifi/components/state/ExternalStateManager.java
---
@@ -0,0 +1,63 @@
+/*
+ * Licensed to the Apache
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69829390
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/ConsumeKafka.java
---
@@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69828743
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/TestGetKafka.java
---
@@ -166,4 +170,44
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/611
This was merged to `0.x`. I will open a new PR with the changes for
`master`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user alopresto closed the pull request at:
https://github.com/apache/nifi/pull/611
---
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
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69828024
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/GetKafka.java
---
@@ -481,4 +496,51 @@ private
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69827581
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/GetKafka.java
---
@@ -481,4 +496,51 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69827217
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/GetKafka.java
---
@@ -218,11 +232,13 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/563#discussion_r69827142
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/GetKafka.java
---
@@ -184,6 +195,9 @@
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
@ijokarumawak I believe you're right about it only being Kafka. I looked
through them as well and couldn't find an instance of external state.
While surprised I am definitely happy because
Github user asfgit closed the pull request at:
https://github.com/apache/nifi-minifi/pull/29
---
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
thanks Bryan, will do.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/conditional-Listen-Syslog-tp12652p12665.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
That probably makes sense. You may not even need back-pressure at all
between ListenSyslog -> Control Rate, this way the data will just queue up
there.
I guess it depends how fast your syslog data is coming in and how long you
think spark will be down.
NiFi will swap out flow files to disk when
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/612
---
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
Thanks Bryan, then I guess in my case for the time being, I am going to use
it like syslog processor-> control rate processor->data output port->spark
application , and apply back pressure like really huge between syslog
processor -> control rate processor and very small back pressure between
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/608
---
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
I agree with everything Joe said, but just wanted to elaborate on one
point...
Currently the way ListenSyslog is implemented [1], UDP and TCP both share
the same logic that offers a message to an internal blocking queue with a
100 ms wait [2].
We should consider changing this for TCP so that it
thanks Joe, its a TCP protocol, and the sender is Qradar, which can buffer
very well up to 60 days of data is what they say, but yes , I am thinking
using NIFI as a buffer is a good idea like you said. KAFKA is also a good
idea, but we might stick to NIFI alone.
But will confirm with the other
Hello
Is this syslog via UDP or is it via TCP? If it is UDP then there
isn't much we can do to push back on the sender. If it is TCP then we
certainly will stop bringing in new data which in turn should
effectively push back but I'm not sure that will work well because the
sender may not be
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69805319
--- Diff: LICENSE ---
@@ -0,0 +1,235 @@
+
+ Apache License
+ Version 2.0, January 2004
Pradeep,
You can configure back pressure on the connection from the ListenSyslog to
the output port.
It can be configure to use data size or number of objects, by selecting the
Settings tab on the connection.
To get to the settings tab, right click on the connection once it is
highlighted.
Once
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/612
+1
Reviewed code, did a contrib check build, created a cluster to demonstrated
the problem and then recreated with the fix and the issue was resolved. Thanks
Mark will merge it in to 0.x
hi there, I am scratching my head to see if there is something in NIFI I can
do, I have a ListenSyslog processor ->data output port->Spark application.
So if my Spark application is down, I would like to cut off ListenSyslog
processor as well so that I would not loose data being pushed, is there a
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69803280
--- Diff: minifi-docs/LICENSE ---
@@ -0,0 +1,235 @@
+
+ Apache License
+ Version 2.0,
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69803232
--- Diff: README.md ---
@@ -18,7 +18,100 @@ MiNiFi is a child project effort of Apache NiFi
## Table of Contents
+-
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69802769
--- Diff: minifi-docs/LICENSE ---
@@ -0,0 +1,235 @@
+
+ Apache License
+ Version
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69802803
--- Diff: LICENSE ---
@@ -0,0 +1,235 @@
+
+ Apache License
+ Version 2.0, January
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69802145
--- Diff: NOTICE ---
@@ -0,0 +1,9 @@
+Apache NiFi - MiNiFi
+Copyright 2014-2016 The Apache Software Foundation
+
+This product includes
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69802152
--- Diff: README.md ---
@@ -18,7 +18,100 @@ MiNiFi is a child project effort of Apache NiFi
## Table of Contents
+-
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/29#discussion_r69801770
--- Diff: NOTICE ---
@@ -0,0 +1,9 @@
+Apache NiFi - MiNiFi
+Copyright 2014-2016 The Apache Software Foundation
+
+This product includes
GitHub user apiri opened a pull request:
https://github.com/apache/nifi-minifi/pull/29
MINIFI-50 - Update READMEs and adjust docs
* Updating the root project README and providing READMEs for both the
minifi and minifi-toolkit assemblies.
* Adjusting needed LICENSE and NOTICE
Hi Sachin,
We are using logstash/elastic-search (the ELK stack) and Watcher to do this
sort of thing. We find the separation of concerns more reliable and flexible
rather than trying to have NiFi monitor itself.
Cheers,
Chris McDermott
Remote Business Analytics
STaTS/StoreFront Remote
HPE
Team,
I have a requirement to send email notification for any failure in Apache
Nifi flow. I know that we have PutEmail processor to achieve this task but
it has to be attached to each processor and moreover it shoots email for
all the flow files where as I am interested in knowing yes failure
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/611
Thanks @alopresto! The changes look good. I have verified the changes
locally in a secured cluster.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user moranr commented on the issue:
https://github.com/apache/nifi/pull/604
â**NIFI-2031** looks good
For **NIFI-2036,** NiFi logo seems to sit a little low after the other
toolbar changes. Please *change* `margin:0 20px 0 15px;` *to* `margin:0 20px
3px 15px;`
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/610
Looks good @markap14! This has been merged to master.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/610
---
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
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/612
NIFI-2159: Fixed bug that caused relationship names not to get added to
fingerprint
You can merge this pull request into a Git repository by running:
$ git pull
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/611
Reviewing...
---
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
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/611
NIFI-2119 Fixed 0.7.0 release blocker for cluster secure communications
The client and server sockets were being treated the same when attempting
to extract the peer certificate DN (server sockets
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/610
Reviewing...
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/576
---
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
GitHub user jfrazee opened a pull request:
https://github.com/apache/nifi/pull/609
NIFI-2142 Cache compiled XSLT in TransformXml
Two other tidbits:
1. This also modifies the XSLT_FILENAME attribute to support expression
language.
2. This updated the test files to have
Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/591
Closing this and resubmitting against master since 0.7 is frozen.
---
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
Github user jfrazee closed the pull request at:
https://github.com/apache/nifi/pull/591
---
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
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/576
+1
Did a contrib check build, reviewed the code and comments were addressed,
and did a functional test using vanilla ES as well as one secured with Shield.
Thanks for the contribution
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/578
---
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
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/578
+1
---
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
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/608
NIFI-2171 Removing list of groups from User
- Making FileAuthorizer not update the resource or action when updating an
AccessPolicy
- Adding corresponding READ policies during initial seeding and
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/576#discussion_r69745504
--- Diff:
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/576#discussion_r69745293
--- Diff:
Hey Andre,
Establishing another client is definitely a priority such that we can have
a foundation for establishing the needed protocols to aid in working toward
centralized management and command and control. With C++ we are starting
from an empty repository and there is a lot of ground to
I haven't looked into a good way to filter them out yet, but I suspect
somehow using the component ids of the components being used after the
Input Port that receives the events.
The reporting task has a configurable batch size which defaults to 1000. So
assuming you are only doing a couple of
Github user asfgit closed the pull request at:
https://github.com/apache/nifi-minifi/pull/28
---
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
That's awesome, I'll just wait for that site-to-site provenance reporting task,
then.
Have you guys figured out a good way to identify those circular provenance
events? I will likely have to use the same cluster for the site-to-site
endpoint.
Joe Gresock
Lockheed Martin Software Engineer Stf
GitHub user scottyaslan opened a pull request:
https://github.com/apache/nifi/pull/607
[NIFI-2018] Update icons used in Context Menu
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scottyaslan/nifi responsiveDevBranch
Hi Joe,
This provides access to the entire Provenance Repository. Typically, what you
would do is use the State Management feature
(ReportingContext.getStateManager()) to store LOCAL-scoped state that includes
the ID of the last provenance event pulled.
You can then get a new batch of
Joe,
You will have to keep track of the last provenance event id that you
queried in order to query for new events.
In 0.7.0 we added a site-to-site provenance reporting task [1] which may
take care of what you need, or at least be an example to base your custom
reporting task from.
The reason
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
Gents,
any further comments? Keen to revisit code if necessary
---
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
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/594
Thanks @scottyaslan! This has been merged to master.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/594
---
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
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/475
Noticed that Apache Zeppelin also use similar profiles:
https://github.com/apache/zeppelin/blob/e0f77d68e813c61d083988e3e167693016418bda/spark-dependencies/pom.xml#L709
---
If your project
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/502
Hey @mans2singh, I'm really busy this week and I won't be able to have a
look before next week :(
In the meantime, you can fix the conflicts against master. And maybe @apiri
will have a chance
70 matches
Mail list logo
