If you are still working on this Aldrin, I noticed that Benson's name is
spelled wrong on the people page [1]
bimargulies Benson Margulie
[1]http://nifi.apache.org/people.html
Dan Bress
Software Engineer
ONYX Consulting Services
From
I'm fine with the package name being changed in 0.3.0
Dan Bress
Software Engineer
ONYX Consulting Services
From: Mark Payne
Sent: Wednesday, August 5, 2015 3:01 PM
To: dev@nifi.apache.org
Subject: RE: Write-Ahead-Log package name change?
Ryan,
Th
a processor and hit configure I'd like to
leave read-only mode and go into edit mode. I'm not sure I'd even want to be
prompted with "do you want to enter edit mode?" here since I obviously do.
Dan Bress
Software Engineer
ONYX Consulting Services
__
+0. Our default branch is set to 'develop', so when you clone apache-nifi from
git, you are automatically looking at the 'develop' branch, right? To me, this
is a straight forward indicator of where I should be working.
I thought we set this up a little while ago to avoid
Ah, I didn't realize that was a github only thing [1], I take-back my early
comment and can now see how this is confusing.
[1]
http://mail-archives.apache.org/mod_mbox/nifi-dev/201501.mbox/%3CCALhtWke141nTsCdA4tHnZXOJ1UGhtZurLwvDsjBxH_G=86n...@mail.gmail.com%3E
Dan Bress
Software Engineer
Joe, thanks for the heads up. I'll delete all of mine, as they are all
resolved in JIRA
NIFI-633: danbress
NIFI-632: danbress
NIFI-680: danbress
NIFI-682: danbress
NIFI-704: danbress
NIFI-735: danbress
Dan Bress
Software Engineer
ONYX Consulting Ser
.
I think it makes more sense to have one processor create one file, then you can
use the flow to visually configure how many copies of the file you want to
make. This should make this processor simpler and more reusable.
Dan Bress
Soft
My stale branches have been deleted.
Dan Bress
Software Engineer
ONYX Consulting Services
From: Mike Drob
Sent: Monday, August 17, 2015 10:07 AM
To: dev@nifi.apache.org
Subject: Re: Lots o branches in git
Also useful is
git remote prune origin
which
tml
[2] http://nifi.apache.org
[3]
https://git-wip-us.apache.org/repos/asf?p=nifi-site.git;a=blob;f=README.md;h=2441a3011cb5163bd440fb04da41b18c8ac21a68;hb=HEAD
Dan Bress
Software Engineer
ONYX Consulting Services
read, and if I get no negative feedback
I'll email INFRA.
Thanks,
Dan Bress
Software Engineer
ONYX Consulting Services
From: Joe Witt
Sent: Wednesday, August 19, 2015 11:49 AM
To: dev@nifi.apache.org
Cc: d...@nifi.incubator.apache.org
Subject: Re: H
formatting the nifi-site/Readme.md which provides instructions for how to
deploy the site.
Does anyone object to me asking INFRA to provide github mirrors for nifi-site
and nifi-maven?
Dan Bress
Software Engineer
ONYX Consulting Services
From: Joe Witt
Sent:
+1
Dan Bress
Software Engineer
ONYX Consulting Services
From: Corey Flowers
Sent: Friday, August 21, 2015 7:28 AM
To: dev@nifi.apache.org
Subject: Re: apache nifi oscon briefing
+1
Sent from my iPhone
> On Aug 21, 2015, at 6:53 AM, "e
No feedback on this one in a few days. I will email INFRA now asking for the
github mirrors.
Dan Bress
Software Engineer
ONYX Consulting Services
From: Dan Bress
Sent: Wednesday, August 19, 2015 12:33 PM
To: dev@nifi.apache.org
Subject: Re: eliminate
Rick,
Can you confirm whether the old processor name still shows up in the "new
processor" UI when you try and drag a new processor on the graph?
Also did you do a 'mvn clean install' on your nar, or just 'mvn install'?
Dan Bress
Software Eng
Rick,
It sounds like the nar contains both the old .class and the new .class
Can you run "mvn clean install" on your nar, then look at the
nar/META-INF/bundled-dependencies/your-processors.jar and see if it contains
both the old class and the new class?
Dan Bress
Software Eng
Rick,
Great. Can you drop that in the lib directory(and make sure you don't have
any other versions of this jar in that lib directory), stop nifi, delete the
work directory, and restart? I think that will get you to where you want to be.
Dan Bress
Software Engineer
ONYX Consulting Ser
assumption
to make? If not, I might be more inclined to agree with your original
suggestion, although keeping that long living branch up to date with all the
changes from master might be a maintenance nightmare.
Dan Bress
Software Engineer
ONYX Consulting Services
OK, sounds good to me. If I had to choose between keeping most of the
communities work 'parked' as PullRequests and patches vs. merged into a 1.X
branch that we keep up to date with master, I'd vote for 1.X branch.
Dan Bress
Software Engineer
ONYX Cons
I think a tag for each release signed by the person who originally released it
would make the most sense to anyone looking at our codebase.
Dan Bress
Software Engineer
ONYX Consulting Services
From: Sean Busbey
Sent: Friday, October 2, 2015 11:35 AM
To
Apache NiFi Committers,
I am working on fulfilling a pull request(NIFI-774), and wanted to make
sure I am doing it right.
These are the steps that I plan on following
1) git remote add yu https://github.com/yu-iskw/nifi.git
2) git pull yu
3) git checkout master
4) git merge --no
Whoops, step 5 should be
5) mvn clean install -Pcontrib-check
On Mon, Oct 12, 2015 at 10:00 AM dan bress wrote:
> Apache NiFi Committers,
>I am working on fulfilling a pull request(NIFI-774), and wanted to make
> sure I am doing it right.
>
>These are the steps that I pl
Devs,
While working on integrating and testing the work Yu did for
NIFI-774/DeleteS3Object, I noticed that a few of the unit tests for the
processors in that AWS bundle(Put and Fetch S3) actually interact with S3
directly, and were marked as @Ignore. If I wanted to un @Ignore them and
actually
[1] https://github.com/blog/967-github-secrets#diff-patch
> [2] https://gist.github.com/piscisaureus/3342247
> [3]
>
> https://help.github.com/articles/checking-out-pull-requests-locally/#modifying-an-inactive-pull-request-locally
>
> On Mon, Oct 12, 2015 at 10:36 AM, dan bress wrote:
gt; >> Dan,
> >>
> >> Yeah this is a good housekeeping item to bring up. My view here is
> >> that B is the only answer. Unit tests should not be calling out to
> >> external services - period.
> >>
> >> Thanks
> >> Joe
> >
Welcome Ricky! Thanks for your contributions and I look forward to you
pushing Apache NiFi forward!
On Wed, Oct 21, 2015 at 3:04 PM Tony Kurc wrote:
> NiFi Community!
>
> Great news!
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Ricky
> Saltzer has accepted the PMC's
Looks well thought out to me! Thanks to all who put the effort into this!
On Fri, Jan 8, 2016 at 6:29 AM Joe Witt wrote:
> Hello NiFi Community
>
> Please review the proposed roadmap and suggest things to add, remove,
> update, prioritize differently.
>
> Over the past year we have had great co
I just tossed some comments on the wikipage.
TL;DR I took a look at generating docs as part of the build months ago. I
think its doable, and someone should pursue it.
On Mon, Jan 18, 2016 at 2:38 PM Joe Witt wrote:
> Oleg,
>
> "Yes, there will be breaking changes. Its not a question of IF, but
I back putting NiFi Javadocs on the website, as it will provide a good
place for new developers to learn how to extend NiFi.
I believe we have a couple of Jira tickets asking for this [1] [2]
Joe, mvn site can definitely do it, whether that is the 'best' way or not
is debatable, since mvn site is
Maybe not exactly "auto-layout" but I would back a notion of having the
components snap to a coarser grain grid than what we currently have.
Sometimes I care a lot about having everything line up in the graph
horizontally and vertically, and it always takes a long time to achieve
this.
I could see
Mark,
I agree with all the points you mention about penalization being
confusing, and I think the ability to apply a penalty to Flowfile's outside
of a processor is a clearer way to express what is happening.
I worry that having the penalty be a property of the connection would
also be confu
reate an index.html
> file? Currently I have only created an additionalDetails.html file.
>
> I will also try to reduce the html code to a minimum and see if it is a
> problem with my code.
>
> Bye,
>
> Uwe
>
> > Gesendet: Freitag, 18. März 2016 um 19:03 Uhr
> > Von
Uwe,
No its not a problem to have both index.html and additionalDetails.html
The NiFi framework generates nearly all of the documentation for your
processor for you. It will generate information about the properties and
relationships your processor exposes to its users. If you need to express
Paul,
Have you tried joining the mailing list using the instructions here:
https://nifi.apache.org/mailing_lists.html
I know in the past, we have had issues with people who aren't
subscribed being unable to send to the list. This seems weird to me as
well, but since you are bringing up som
Russell,
I agree the syntax for multiple DynamicProperties is a little awkward,
and that our documentation could be improved in this situation(I didn't see
reference to @DynamicProperty in the developer doc).
Also Java8 supports the concept of repeatable annotations[1], which
would erase the
Welcome James!
On Wed, May 11, 2016 at 1:15 PM Mark Payne wrote:
> Welcome, James! Glad to have you aboard!
>
> > On May 11, 2016, at 4:10 PM, Joe Witt wrote:
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that James
> > Wing has accepted the PMC's inviation to become a comm
+1
On Wed, Jun 8, 2016 at 7:05 AM Andre wrote:
> +1 on this + a template that matches existing additional.html
> On 8 Jun 2016 04:28, "Bryan Rosander" wrote:
>
> > Hey all,
> >
> > When writing documentation (e.g. the additionalDetails.html for a
> > processor) it would be nice to have the opti
36 matches
Mail list logo
