Github user rickysaltzer commented on the pull request:
https://github.com/apache/nifi/pull/147#issuecomment-176801515
will do - checking on it now
---
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
Github user rickysaltzer commented on the pull request:
https://github.com/apache/nifi/pull/147#issuecomment-176806382
Build and functional testing are a +1 from me. I'll push this out
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/187#issuecomment-176807151
@rpmiskin
Following the RFC 822 guideline (that the MimeMessage class is based on) it
says this about the "From" header:
4.4.1. FROM / RESENT-FROM
Github user rickysaltzer commented on the pull request:
https://github.com/apache/nifi/pull/147#issuecomment-176808901
patch checked into `master`
https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=73c0637
---
If your project is set up for it, you can reply to this email and have y
Github user rickysaltzer commented on the pull request:
https://github.com/apache/nifi/pull/188#issuecomment-176812870
Thanks @joewitt - I'll take a look either today or tomorrow. Yep, post
0.5.0 seems more than likely to get this in good shape. Thanks again
---
If your project is s
Github user PuspenduBanerjee commented on the pull request:
https://github.com/apache/nifi/pull/186#issuecomment-176814383
Closing PR, as found some issue in Integration test. Shall raise a new PR
later.
---
If your project is set up for it, you can reply to this email and have your
Github user PuspenduBanerjee closed the pull request at:
https://github.com/apache/nifi/pull/186
---
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
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/193
NIFI-1447 modified SimpleProcessLogger
Modified SimpleProcessLogger to ensure that whenever is called it prints
full stack trace.
You can merge this pull request into a Git repository by running:
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/194
NIFI-1417 Exposing several connection settings on the Solr processorsâ¦
I was not able to reproduce the exact scenario described in this ticket,
but based on the stack trace I believe exposing some of
Github user rdblue closed the pull request at:
https://github.com/apache/nifi/pull/147
---
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 rdblue commented on the pull request:
https://github.com/apache/nifi/pull/147#issuecomment-176866130
Thanks, @rickysaltzer! I'll close this again.
---
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 projec
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/195
NIFI-1093 added support for handling non-required columns
Mostly based on contribution from Daniel Cave
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
Github user mattyb149 closed the pull request at:
https://github.com/apache/nifi/pull/178
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/193
---
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
We are in the process of automating the pipeline deloyment across multiple
clusters. In our scenario there are two different clusters with their own
pipelines. And the ports are open on both the machines.
When I’m creating the RPG on the sending cluster it failed saying that the
destination is
Github user ledor473 commented on the pull request:
https://github.com/apache/nifi/pull/183#issuecomment-176961200
All very valid points there, I'll have a look at them.
The merge request will be updated with the fixes soon and will also be
up-to-date with the current master
---
I have the cluster in a state with the message on the problem node…
Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed
configuration is not inheritable by the flow controller because of flow
differences: Found difference in Flows:
Local Fingerprint:
170e8ec-5b16-4564
Paresh,
The RPG should communicate with the target instance everything 30 seconds
in the background to discover available ports. A couple of possibilities
1) Which version of NiFi are you running? In 0.4.1 we addressed an issue
that caused the RPGs to not refresh as often as it should [1]. You sh
Paresh,
In the top-right-hand corner of the NiFi UI, there is a Cluster Management
icon. I believe it is the next-to-last icon there.If you click on that icon,
you will be given a dialog that shows all nodes in the cluster, and you can
click the "Disconnect" iconto remove a node from the cluster
Thanks.
On 1/29/16, 2:07 PM, "Mark Payne" wrote:
>Paresh,
>In the top-right-hand corner of the NiFi UI, there is a Cluster
>Management icon. I believe it is the next-to-last icon there.If you click
>on that icon, you will be given a dialog that shows all nodes in the
>cluster, and you can click
Version is 0.4.1. Instances are not secured.
Paresh
On 1/29/16, 2:02 PM, "Matt Gilman" wrote:
>Paresh,
>
>The RPG should communicate with the target instance everything 30 seconds
>in the background to discover available ports. A couple of possibilities
>
>1) Which version of NiFi are you runni
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/147#issuecomment-177054637
@rdblue There was a comment @joewitt had left on the associated ticket.
https://issues.apache.org/jira/browse/NIFI-1193?focusedCommentId=15123007&page=com.atlassian.jir
22 matches
Mail list logo
