Github user rpmiskin closed the pull request at:
https://github.com/apache/nifi/pull/187
---
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 enab
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/201#issuecomment-178369880
The Travis CI failure is due to my use of `java.util.Base64` which was
introduced in Java 8. Working on switching out to
`org.apache.commons.codec.binary.Base64` but thi
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/200#issuecomment-178347191
Will fix as well as the merge conflict
---
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 n
Thanks Joe,
I'm finishing up reviewing/testing 1107, I was going to pull the trigger on
versioning all the poms, but I think i'll wait until more of these close to
help people merging.
Tony
On Mon, Feb 1, 2016 at 5:22 PM, Joe Witt wrote:
> Team,
>
> We still have quite a few tickets for 050 out
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/187#issuecomment-178328472
Hello @rpmiskin Do you mind closing this PR? Looks like @JPercivall just
forgot to amend the comit entry to ensure it said 'This closes #187' but it
does show as merged.
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/200#issuecomment-178325971
Had checkstyle violations for unused imports:
> [INFO] --- maven-checkstyle-plugin:2.15:check (check-style) @
nifi-amqp-processors ---
[WARNING]
src/test/java/o
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/185
---
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 enable
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/201
NIFI-1257 and 1259
NIFI-1257
NIFI-1259
Added the mechanics for additional strong `Key Derivation Functions` (KDF)
including `PBKDF2`, `Bcrypt`, and `Scrypt` as well as `keyed ciphers` (
Timothy
In short it’s very possible. I personally haven’t done that, but I have written
some custom code submitting jobs to YARN which I am assuming would be very
similar.
Would be happy and actually interested to take it a bit further. Could you
elaborate on the use case a bit more? For examp
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/197#issuecomment-178287033
@PuspenduBanerjee We are currently in the process of releasing 0.5 which is
imminent. We'll be happy to help you through this (review, polish etc) once 0.5
is out. Hope you
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/194
---
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 enable
Github user PuspenduBanerjee commented on the pull request:
https://github.com/apache/nifi/pull/197#issuecomment-178252892
@joewitt For Non-Uniform charset attached piece should work.
```java
/**
* @param rawBytes
* @param patternToMatch
* @return
Team,
We still have quite a few tickets for 050 outstanding so freezing for
the RC just isn't there yet. Of the tickets below all are in review
many of which after much discussion and progress. Expect several of
them to close very soon. Once we have them knocked out Tony can do
the RC process.
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/180#discussion_r51490929
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchPr
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/185#discussion_r51488029
--- Diff:
nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/java/org/apache/nifi/processors/script/InvokeScriptedProcessor.java
---
@@
Hi Folks,
Forgive me as I'm new to Nifi. The tool seems fantastic, the UI is super easy
to use. It was easy to extend and build a custom processor which is great.
Looking at our processing, we're curious if we could use Nifi to replace some
of our batch processes. Setting up some of the basic
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/194#issuecomment-178209934
@markap14 thanks for reviewing!
Good point about the isSet(). I was thinking someone could remove the
default value, but didn't realize that isn't possible. I'll c
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/180#discussion_r51483875
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchPr
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-178198337
There needs to be support added for passing username/password (specifically
for shield integration)
---
If your project is set up for it, you can reply to this email a
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/180#discussion_r51482142
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchPr
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/194#issuecomment-178187346
I don't know how to really reproduce the issue either, but i agree that
these are good properties to introduce. All new properties have defaults so
flows will not be brok
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/194#discussion_r51478213
--- Diff:
nifi-nar-bundles/nifi-solr-bundle/nifi-solr-processors/src/main/java/org/apache/nifi/processors/solr/SolrProcessor.java
---
@@ -120,6 +202,22 @@ pro
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/194#discussion_r51478207
--- Diff:
nifi-nar-bundles/nifi-solr-bundle/nifi-solr-processors/src/main/java/org/apache/nifi/processors/solr/SolrProcessor.java
---
@@ -120,6 +202,22 @@ pro
Thanks for the clarification.
On 2/1/16, 11:59 AM, "Joe Witt" wrote:
>Sorry - i only mean to recommend clearing out the flow config on the
>node including the templates on the node. When it rejoins the cluster
>it will inherit the flow from the NCM.
>
>On Mon, Feb 1, 2016 at 2:51 PM, Paresh Sha
The Nodes will not have a flow.tar. Only the NCM has a flow.tar (*do not
delete your flow.tar*). The Nodes will get both their templates and
flow.xml.gz from the NCM on startup, so it is safe to remove them on the
node.
On Mon, Feb 1, 2016 at 2:48 PM, Joe Witt wrote:
> Paresh,
>
> In the log
Sorry - i only mean to recommend clearing out the flow config on the
node including the templates on the node. When it rejoins the cluster
it will inherit the flow from the NCM.
On Mon, Feb 1, 2016 at 2:51 PM, Paresh Shah wrote:
> But our scenario is as follows.
>
> 1. We will deploy a cluster w
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/200
NIFI-865 added initial support for AMQP publish/subscribe
added initial documentation and testing. More tesing will be added
You can merge this pull request into a Git repository by running:
$ git
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/199#issuecomment-178159306
Closing it after initial review. Will open a new one once all comments are
addressed and cleanup.
---
If your project is set up for it, you can reply to this email and have
Github user olegz closed the pull request at:
https://github.com/apache/nifi/pull/199
---
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 enabled
But our scenario is as follows.
1. We will deploy a cluster with NCM and Primary.
2. We deploy out pipelines.
3. Add slave nodes to the cluster.
In this scenairo we cannot be wiping way the flow.* files since we will
loose the pipelines, right?
Paresh
On 2/1/16, 11:48 AM, "Joe Witt" wrote:
>P
Paresh,
In the log it says "Caused by:
org.apache.nifi.controller.UninheritableFlowException: Proposed
configuration is not inheritable by the flow controller because of
flow differences: Found difference in Templates:". So on your node
blow away both the flow.xml.gz, flow.tar, and the templates
Here’s the scenario.
1. Deploy Nifi Cluster :
- NCM
- Pirmary
- Node.
2. Verified that everything is OK.
3. I then disconnected the slave Node and deployed some pipelines on the
cluster.
4. Now I tried to bring up the slave node. It gives the following error.
2016-02-01 19:41:05,
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51459684
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/ConsumeAMQP.java
---
@@ -0,0 +1,122 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51445239
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/test/resources/log4j.properties
---
@@ -0,0 +1,22 @@
+# Licensed to the Apache Software
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/195
---
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 enable
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51444798
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/test/resources/log4j.properties
---
@@ -0,0 +1,22 @@
+# Licensed to the Apache Softw
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51444624
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPConsumer.java
---
@@ -0,0 +1,78 @@
+/*
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r5168
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPConsumer.java
---
@@ -0,0 +1,78 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51444249
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPPublisher.java
---
@@ -0,0 +1,128 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51443924
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPWorker.java
---
@@ -0,0 +1,104 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51443717
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPConsumer.java
---
@@ -0,0 +1,78 @@
+/*
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51442712
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPConsumer.java
---
@@ -0,0 +1,78 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51442275
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPConsumer.java
---
@@ -0,0 +1,78 @@
+/*
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51442155
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPWorker.java
---
@@ -0,0 +1,104 @@
+/*
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51441942
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPPublisher.java
---
@@ -0,0 +1,128 @@
+
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51441537
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPConsumer.java
---
@@ -0,0 +1,78 @@
+/*
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51441125
--- Diff: nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/pom.xml ---
@@ -0,0 +1,74 @@
+
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/199#discussion_r51441043
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-nar/src/main/resources/META-INF/LICENSE
---
@@ -0,0 +1,319 @@
+
+
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/199
[REVIEW ONLY]]NIFI-865 added initial support for AMQP publish/subscribe
Still working on docs and tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-178023848
If the "Identifier Attribute" is being left as the attribute containing the
identifier then the "ATTRIBUTE_KEY_VALIDATOR" should be used instead of
"NON_EMPTY_VALIDATOR
50 matches
Mail list logo
