Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/455
---
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 mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/452#issuecomment-220457062
With the builders included, looks good to me.
@jtstorck @alopresto Thoughts?
---
If your project is set up for it, you can reply to this email and have your
Github user eorgad commented on the pull request:
https://github.com/apache/nifi/pull/453#issuecomment-220467272
Taking a dipper look at this, the the ScpTo.java code uses the following:
...
// exec 'scp -t rfile' remotely
String command="scp " + (ptimestamp ? "-p"
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/445#issuecomment-220438461
Thanks for tackling this. Will merge. Thanks!
---
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
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/452#discussion_r63956868
--- Diff:
nifi-api/src/main/java/org/apache/nifi/authorization/AccessPolicy.java ---
@@ -0,0 +1,291 @@
+/*
+ * Licensed to the Apache Software
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/445
---
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 mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/452#issuecomment-220469545
@alopresto Great comment about the UserService. The reason we cannot do
that directly is the extension point that is getting discovered is an
Authorizer. However, this
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/452#issuecomment-220464739
@mcgilman thanks for the response above. It feels a little to me like the
authorizer has gotten conflated with user and group management tasks. If the
authorizer'
We have a requirement to run NiFi in an approved app server. Is it
possible to do that? If not, is there a plan to support that? Thanks.
Thanks to everyone making this now open sourced tool awesome.
I can't find anything that directly links the 2.
I want to use Nifi to coordinate page scraping, parsing, and finally throw
Titan data for graphs.
Do I have to use Kafka or Spark for this?
I'm looking at the output mechanisms
Github user mosermw commented on the pull request:
https://github.com/apache/nifi/pull/453#issuecomment-220499039
@eorgad your interest and willingness to get involved with the NiFi
community is certainly appreciated. In this case, I don't think the Travis
build failed on the code
Pat
It looks like Titan can be backed by Apache Cassandra or Apache HBase.
NiFi can deliver to both of those. Would that take care of what
you're looking to do?
Thanks
Joe
On Thu, May 19, 2016 at 11:16 PM, Pat Trainor wrote:
> Thanks to everyone making this now open
Simon,
Are you suggesting attributes similar to UnpackContent?
If yes, seems like a great approach.
Cheers
On 19 May 2016 14:50, "Simon Elliston Ball"
wrote:
Fantastic idea!
Would SplitEmail not make sense to divide by the mime boundary? If you add
fragment
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/455
NIFI-1898 fixed @OnSchedule methods to accept ProcessContext
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1898
Alternatively
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/366
---
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
Joe,
That's exactly the idea.
I envision to, from, cc, connecting host (src_ip of the last hop), subject,
time and possibly an option to iterate over the headers, adding
discretionary key value pairs for things like spamassassin scores, etc.
I pkan to keep things simple so I don't intend to
Arturo,
That makes sense.
I created this JIRA to capture the issue and conversation:
https://issues.apache.org/jira/browse/NIFI-1902
Feel free to comment on it if I missed anything.
-Bryan
On Thu, May 19, 2016 at 10:27 AM, Arturo Michel <
arturo.mic...@leotech.com.sg> wrote:
> HI Bryan,
>
>
Yes, exactly. The challenge would be what to do with the mime boundary header
(include with content, or dump and rebuild with a merge).
Simon
> On 19 May 2016, at 12:45, Andre wrote:
>
> Simon,
>
> Are you suggesting attributes similar to UnpackContent?
>
> If yes,
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/452#issuecomment-220307255
@alopresto Thanks for the very thorough review! This API is designed
strictly for handling the persistence of access policies which would also
include Users and Groups.
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/454#discussion_r63874050
--- Diff:
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/454#issuecomment-220330762
@markap14 When canceling revision claims for Connectable components in the
verifyXxx() methods, DAO access will not return null so you do not need to
check for it there.
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63900979
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,338 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63903305
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,338 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63907479
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63908853
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63902327
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,338 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63902702
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,338 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63907025
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63906843
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63918531
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
GitHub user benqiu2016 opened a pull request:
https://github.com/apache/nifi-minifi-cpp/pull/2
Minifi 6
MINIFI-6: First drop of working C++ MiNiFi
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/nifi-minifi-cpp MINIFI-6
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63920230
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63919624
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63917779
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63918463
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63918814
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63919932
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,237 @@
+/*
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/403#issuecomment-220420085
@pvillard31 Thanks for tackling this. I was working on some API type items
and wanted to ensure this got addressed before too much effort went into that
and the conflicts
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/392#issuecomment-220432007
@olegz pushed out a commit addressing the comments (sans the SSL Context
Service property mapping, due to my comment above)
---
If your project is set up for it, you
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/455#issuecomment-220436789
Was able to build and verify that the Flume processors work as anticipated
with this change. Thanks! Will merge in.
---
If your project is set up for it, you can reply to
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/403
---
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
Hey folks,
As a heads up, PR #403 [1]/NIFI-1811 is to be merged in imminently. This
is part of cleaning up some of our code debt as we move toward 1.0 and
removing of the ProcessorLog which was deprecated/supplanted by
ComponentLog.
For contributors, if possible, it would be desirable to make
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63941204
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
43 matches
Mail list logo