Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/450#issuecomment-219610061
Appreciate the spirit but this is not something you need RTC for. +1 in
any event.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/450
Added PGP key to KEYS file.
Added my public PGP key to the KEYS file to allow developers to verify
signatures.
You can merge this pull request into a Git repository by running:
$ git pull
Congratulations, Joe. Great addition to the team.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On May 16, 2016, at 8:08 PM, Tony Kurc wrote:
>
> Hooray!
> On May 16, 2016 11:00 PM, "Joe
Hooray!
On May 16, 2016 11:00 PM, "Joe Witt" wrote:
> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Joe Percivall has accepted the PMC's invitation to join the Apache
> NiFi PMC. We greatly appreciate all of Joe's hard work and generous
>
On behalf of the Apache NiFI PMC, I am very pleased to announce that
Joe Percivall has accepted the PMC's invitation to join the Apache
NiFi PMC. We greatly appreciate all of Joe's hard work and generous
contributions to the project. We look forward to his continued
involvement in the project.
Github user alopresto commented on a diff in the pull request:
https://github.com/apache/nifi/pull/442#discussion_r63457225
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/test/groovy/org/apache/nifi/controller/PositionScalerSpec.groovy
---
Github user alopresto commented on a diff in the pull request:
https://github.com/apache/nifi/pull/442#discussion_r63457158
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/test/groovy/org/apache/nifi/controller/PositionScalerSpec.groovy
---
Github user alopresto commented on a diff in the pull request:
https://github.com/apache/nifi/pull/442#discussion_r63456899
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/PositionScaler.java
---
@@ -0,0
Tony: Good point and probably fair game. It would need to be really
urgent and really specific I think though. Otherwise no need to rush.
Matt: Yeah that is a great idea.
AdamL: Thanks for offering to setup a zoom. I'll try to do it and if
good will send details on meetup invite. If not I'll
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/424#discussion_r63453123
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-transform-json-ui/src/main/java/org/apache/nifi/web/standard/api/processor/ProcessorResource.java
---
@@
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/424#discussion_r63452681
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java
---
@@
Joe - if a bug is discovered during the hackathon and patch developed,
would this be an appropriate short turnaroundJIRA/patch/merge type
situation?
On May 16, 2016 5:31 PM, "Matt Burgess" wrote:
> One thing that could be done to enable demos while still having
> PRs/patches
Github user jtstorck commented on the pull request:
https://github.com/apache/nifi/pull/449#issuecomment-219592267
Closed PR at the request of @alopresto.
---
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 jtstorck closed the pull request at:
https://github.com/apache/nifi/pull/449
---
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 alopresto commented on the pull request:
https://github.com/apache/nifi/pull/449#issuecomment-219586093
@jtstorck because I did not merge this into the `master` branch, the phrase
`This closes #449.` in the commit message will not close this PR. Can you
please manually
In my NiFi cluster environment, for a given flow, each node in the cluster is
producing afinal FlowFile that is written to HDFS.
I needed to append NodeID to filename attribute (e.g., node1_filename1.tar) so
that files written to HDFS has unique name and I can easily identify which node
Github user eorgad commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63443355
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user eorgad commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63443270
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutSCP.java
---
@@ -0,0 +1,93 @@
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/404
---
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
Ricky,
Glad we could help. The way we have the files organized separates the concern
of authentication (login-identity-providers.xml) and authorization
(authority-providers.xml). I understand it can be confusing. We’ll take a look
at cleaning up the documentation/making that information more
Ah I believe I've figured it out. It appears I was getting confused by the
difference between authority-providers and the login-identity-providers as
they have identical stanzas. The solution was to add the provider to the
login-identity-providers.xml.
Thanks so much for your sample configs,
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/447#issuecomment-219567073
Should have mentioned that you're not required to put the "Signed-off-by"
when merging your own commits. As long as they've been reviewed by another
committer, you can
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/449#issuecomment-219563962
@jtstorck now when the build is run, full test output is provided as
follows:
```
[INFO] --- maven-surefire-plugin:2.18:test (default-test) @
Hi,
Because this seems to be a more complex mapping, using ExecuteScript with
Groovy (or another supported scripting language if you’re more comfortable with
one) to do the translation may make sense. Matt Burgess has provided detailed
tutorials in a variety of languages on his blog [1].
Joe, thanks for your reply. I wonder whether a typo in my example might have
made what I would like to achieve slightly confusing. My mapping file looks
like this (note value in bold as opposed to "2" as included in my first
post":
Header1;Header2;Header3
A;some text;*A2 *
Am I correct in
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/449#issuecomment-219556910
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
One thing that could be done to enable demos while still having PRs/patches go
through the Apache process is to have the Organizer create a hackathon branch
off their fork, and merge in any patches/PRs that are demo-able, then show the
hackathon goodness at the end. Then the regular process
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/439#discussion_r63429069
--- Diff:
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63426185
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/439#discussion_r63425823
--- Diff:
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/439#discussion_r63425553
--- Diff:
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/439#discussion_r63425128
--- Diff:
Team,
I wanted to shoot out a note to gather input on some rules of
engagement so to speak for running a nifi hackathon/meetup. A few of
us in the DC/MD area have one planned soon [1].
What I'd like to send out to the meetup group are some ground rules
for how the meetup will operate. It is
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/448
NIFI-1554: Introducing component level revision and authorization for
ControllerService and ReportingTasks
NIFI-1554
- Phase one of introducing revision and authorization for
ControllerServices
Github user andrewmlim commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-219545549
For the âClient IDâ property help: âCorresponsâ should be changed
to âCorrespondsâ.
---
If your project is set up for it, you can reply to this email
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/439#discussion_r63423341
--- Diff:
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/404#issuecomment-219540129
Cool, let me do a final review and I'll merge
---
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 pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/404#issuecomment-219539616
Thanks @olegz
PR updated
---
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 olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63419802
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63419525
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63418280
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/446#issuecomment-219535028
Look good @markap14
Thanks! I've 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
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/446
---
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 jvwing commented on the pull request:
https://github.com/apache/nifi/pull/447#issuecomment-219530068
@alopresto, thanks for your help. Your cheatsheet is a great idea, I would
have missed the 0.x branch without it.
---
If your project is set up for it, you can reply to
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63414327
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63412890
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutSCP.java
---
@@ -0,0 +1,93 @@
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/430#discussion_r63410760
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63408651
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user pvillard31 closed the pull request at:
https://github.com/apache/nifi/pull/438
---
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 jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/430#discussion_r63405577
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FlowDebugger.java
---
@@ -0,0 +1,414
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/430#discussion_r63405091
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63404486
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63403903
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/GetSCP.java
---
@@ -0,0 +1,118 @@
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/447#issuecomment-219510269
It definitely takes some getting used to. Here is a
[cheatsheet](https://gist.github.com/alopresto/c05485f80799cd3ba02461b07f1e82de)
I wrote for myself. This PR is a
Github user jvwing commented on the pull request:
https://github.com/apache/nifi/pull/447#issuecomment-219509273
My powers are weak :(. I waded through the new committer docs that seem
heavy on Subversion setup, and I have not verified git access. If you don't
mind me thrashing on
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/416#issuecomment-219508344
Ok, I guess I jumped the gun too soon and spoke of my personal preference
as if it was a decision.
Anyway, will be reviewing.
---
If your project is set up for it,
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/416#issuecomment-219503574
@olegz i am not aware of any discussion or decision to avoid adding things
to standard processors. I think for this one it is a perfectly valid place.
For things with
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/404#issuecomment-219502908
@pvillard31 there is a merge conflict in
```
CONFLICT (content): Merge conflict in
nifi-mock/src/test/java/org/apache/nifi/util/TestStandardProcessorTestRunner.java
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/416#issuecomment-219501349
@eorgad First, thank you for your contribution. This is definitely
something people had asked for.
Now, . . . . I see that you added it to the standard processors. What
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/438#issuecomment-219498693
@pvillard31 could you please close this PR? I've merged both but forgot to
amend the commit message on this one to automatically close.
---
If your project is set up for
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/447#issuecomment-219498359
Looks good to me. Want to merge it yourself with your new committer powers?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/347
---
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 pull request:
https://github.com/apache/nifi/pull/347#issuecomment-219489958
merging
---
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
This post has a diagram of what Joe described:
https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html
-Bryan
On Mon, May 16, 2016 at 10:20 AM, Joe Witt wrote:
> Dale,
>
> The common pattern here is to use NiFi's site-to-site
I was wondering if there was a way for the NCM to distribute FlowFiles to
different nodes.
Currently I see that all of the nodes in my cluster run the same dataflow. I
know I can restrict certain processors to the primary node, but it seems
like the NCM does not distribute the FlowFiles to
Dale,
The common pattern here is to use NiFi's site-to-site function to
distribute the load to the rest of the cluster. So you'd setup a
remote input port on your flow and then connect the output of your
primary only processor to a remote process group of that same cluster
using that new port.
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/439#discussion_r63344780
--- Diff:
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/446#discussion_r63344217
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core-api/src/main/java/org/apache/nifi/controller/Template.java
---
@@ -0,0
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/446#discussion_r63343732
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core-api/src/main/java/org/apache/nifi/controller/Template.java
---
@@ -0,0
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/446
NIFI-1801: Scope Templates to Process Groups
Also includes a few bug fixes that were not necessarily explicitly related
to templates being scoped to Process Groups but that are required in order to
70 matches
Mail list logo