Woo hoo. We have zero items left in the 1.1.0 JIRA list and have
gotten a lot of solid input from testing thus far.
Will kick out the RC this evening.
Thanks
Joe
On Wed, Nov 23, 2016 at 4:08 PM, Tony Kurc wrote:
> awesome news!
>
> On Wed, Nov 23, 2016 at 3:51 PM, Joe Witt wrote:
>
>> it was
awesome news!
On Wed, Nov 23, 2016 at 3:51 PM, Joe Witt wrote:
> it was approved for continued pre-existing usage until April 2017.
> Sent a note on this earlier which you've probably just run into by
> now. We're good to go.
>
> On Wed, Nov 23, 2016 at 3:46 PM, Andre wrote:
> > Joe,
> >
> > M
it was approved for continued pre-existing usage until April 2017.
Sent a note on this earlier which you've probably just run into by
now. We're good to go.
On Wed, Nov 23, 2016 at 3:46 PM, Andre wrote:
> Joe,
>
> May I ask what was the decision?
>
> Kind regards
>
> On 24 Nov 2016 01:13, "Joe W
Joe,
May I ask what was the decision?
Kind regards
On 24 Nov 2016 01:13, "Joe Witt" wrote:
> Some good news - we can put our twitter processor back in the game.
>
> Legal VP at Apache just sent out the decision.
>
> Will immediately restore that to action and put in the follow-on
> ticket to e
release notes here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.1.0
migration notes here:
https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
Will kick out an RC today or in next day or two hopefully.
Thanks
Joe
On Wed, Nov 23, 2016 at 9:
Some good news - we can put our twitter processor back in the game.
Legal VP at Apache just sent out the decision.
Will immediately restore that to action and put in the follow-on
ticket to ensure the twitter4j library moves away from the old Json
lib (there is a PR to replace it). We can only k
Awesome. Your prompt and detailed feedback is very much appreciated!
On Tue, Nov 22, 2016 at 12:47 PM, Joe Witt wrote:
> mike - also to clarify based on what you brought up I updated the JIRA
> description as follows
>
> The following also would be true:
> 1) Apache NiFi 1.0.0 repositories sho
mike - also to clarify based on what you brought up I updated the JIRA
description as follows
The following also would be true:
1) Apache NiFi 1.0.0 repositories should work just fine when applied
to an Apache NiFi 1.1.0 installation.
2) Repositories made/updated in Apache NiFi 1.1.0 onward would
Mike - yeah good catch and good question. It does support the old
format. We've always been pretty good about being diligent to allow
folks to upgrade and it honor existing state and in many cases
configurations and it would automatically port them over. What has
always been far more problematic
After seeing "Repositories now support rollback" in the release notes and
reading NIFI-2854 [1], I have a question.
Are repositories created using NiFi 1.0.0 compatible with NiFi 1.1.0
software? This is the goal that the ticket seems to indicate with 1.1.0
onward, but it's not clear whether 1.0.0
Thanks James. Will add the AWS stuff now. The generate flow file
I'll leave off since it is mostly a developer/debug tool unless you
disagree.
Thanks
Joe
On Tue, Nov 22, 2016 at 12:08 PM, James Wing wrote:
> Going through the tickets, it seems like quite a release. A few more
> things for you
Going through the tickets, it seems like quite a release. A few more
things for your list:
GenerateFlowFile updated to support literal/expression content and
attributes
AWS-related:
* New processors PutCloudWatchMetric, PutKinesisStream
* Updated processors PutS3Object (content type, signer opti
I've reviewed NIFI-3064 and it's good to go, would like to add that one as well.
Thanks,
Matt
On Tue, Nov 22, 2016 at 10:51 AM, Joe Witt wrote:
> thanks Joe and Andy. Have those on the list now.
>
> On Tue, Nov 22, 2016 at 5:09 AM, Joe Gresock wrote:
>> I'm biased, but I think the new Query /
thanks Joe and Andy. Have those on the list now.
On Tue, Nov 22, 2016 at 5:09 AM, Joe Gresock wrote:
> I'm biased, but I think the new Query / Scroll Elasticsearch processors are
> pretty big ;)
>
> On Tue, Nov 22, 2016 at 9:02 AM, Andy LoPresto wrote:
>
>> Important to call out in the security
I'm biased, but I think the new Query / Scroll Elasticsearch processors are
pretty big ;)
On Tue, Nov 22, 2016 at 9:02 AM, Andy LoPresto wrote:
> Important to call out in the security section that
> login-identity-providers.xml is now covered by encrypted config, and
> flow.xml.gz processor prop
Important to call out in the security section that login-identity-providers.xml
is now covered by encrypted config, and flow.xml.gz processor property
encryption/nifi.sensitive.props.key value can now be migrated by the
command-line tool (second part pending completion of NIFI-3024).
Andy LoPre
matt
i'll add a wiki page or set of instructions linked from the release notes.
all,
walked through the 250 or so JIRAs in the 1.1.0 release and pulled out
highlights. The items noted are as follows. Will likely reduce this
down further for the release notes but wanted to put this out in case
Is there a good spot for us to put instructions on how to build the
Twitter processor and/or the Social Media NAR in the meantime? Maybe a
Wiki page or something simple to say "go to this directory, run this
Maven command, drop the NAR into your deployment..." ?
On Mon, Nov 21, 2016 at 9:34 PM, Jo
Team,
We appear to be very close. Andy is working NIFI-3024 but otherwise
it is focus on testing.
I'm going to prep the RC and release notes now. Unfortunately the
twitter changes for json.org will need to remain. Consensus forming
on the legal-discuss thread regarding a grace period has been
Andy,
Great to see NIFI-3050 implemented and certainly good news that NiFi 1.1.0
is set to include a number of security related improvements.
On Thu, Nov 17, 2016 at 2:38 PM, Andy LoPresto wrote:
> Just updating this thread that NIFI-3050 [1] and NIFI-3051 [2] have been
> added to my plate fo
Just updating this thread that NIFI-3050 [1] and NIFI-3051 [2] have been added
to my plate for this release. Coordinated with Joe Witt and they should both be
included.
[1] https://issues.apache.org/jira/browse/NIFI-3050
[2] https://issues.apache.org/jira/browse/NIFI-3051
Andy LoPresto
alopre..
Team
There is a thread on apache legal-discuss that might allow for a
graceperiod of continued usage of the json library. Am going to keep
a close eye on this and if VP Legal approves we'll be able to keep the
twitter processors in which is definitely a good thing. Will advise
Thanks
Joe
On We
I've noticed an issue with the per-instance class loading capability
introduced in NIFI-2909 where the additional classpath resources can get
incorrectly removed from the class loader.
I was able to reproduced this with a unit test and have a fix ready. I
believe this is important and needs to go
I have two items that I would like to wrap up prior to creating an RC for
1.1.0. NIFI-2949 addresses some UX issues around Remote Process Group port
configuration. The work is already completed and I will be reviewing it
this today. Additionally, following recent interest on the mailing list,
I'd l
The code is within the twitter4j library itself. I filed a request to
twitter4jg. The most likely case is we will need to submit a PR to them.
However, I don't see this as something that should delay the release. We
can provide instructions for folks wanting to use the processor during the
time
I understand there was a discussion thread within the NiFi community for this
as well and I missed responding to that at that time. It just seems to me like
JSON processing is necessary for GetTwitter, which is incredibly useful for
demonstrating NiFi’s ability to read from a high volume stream
I’m working with Bryan Rosander to close out NIFI-3024, NIFI-2655, and
NIFI-2653. I believe Matt Burgess is working on NIFI-3011 and we investigated
some alternate TLS config options for the new version of the client library.
Is there any alternative to excluding the GetTwitter processor? Using
Team
Very happy to see that we are down to three items remaining tagged to
1.1.0. Solid effort over the recent weeks to close the gap including work
to get past the now category x Jason dependency we had. The most notable
impact from that is the wildly popular GetTwitter processor, the fav new
n
Ryan
Not officially but I think we should try to close this thing out and
start a vote in the next week or two at most.
I'm going through the tickets again now. There is also a new issue of
the json-p license falling out of favor in Apache legal terms and
becoming Category-X. Am looking into th
Joe - Is there a target date for 1.1?
On Thu, Oct 27, 2016 at 10:50 AM, Joe Witt wrote:
> Team,
>
> Just an update on things with working toward an Apache NiFi 1.1.0
> release. There are still about 33 JIRAs there now and some are
> awaiting review and are some are under active progress. Yet th
Team,
Just an update on things with working toward an Apache NiFi 1.1.0
release. There are still about 33 JIRAs there now and some are
awaiting review and are some are under active progress. Yet there is
good traction and progress. I think we should just stay vigilant with
what makes it in and ke
Team,
There are 31 open JIRAs at present tagged to Apache NiFi 1.1.0. Let's
avoiding putting more in there for now at least without a discussion.
Of the 31 JIRAs there the vast majority need review so we should be
able to close these down fairly quickly as long as we don't let the
list grow.
Tha
Joe,
Appreciate the offer it isn't my PR. I was just using it as an example. All
mine are currently closed, which I greatly appreciate.
Cheers,
Edgardo
On Friday, October 14, 2016, Joe Witt wrote:
> Edgardo,
>
> You mentioned a PR from August. I'd be happy to help you work that
> through revi
Edgardo,
You mentioned a PR from August. I'd be happy to help you work that
through review.
Thanks
Joe
On Fri, Oct 14, 2016 at 10:45 AM, Edgardo Vega wrote:
> I have agreed that at this point a release is important. My goal was try to
> squeeze in a much goodness as possible into the release, b
I have agreed that at this point a release is important. My goal was try to
squeeze in a much goodness as possible into the release, but the important
bug fixes should come first. Getting 1.x into a state where the release
notes don't say that it is geared toward developers and testers is really
hu
Edgardo,
Thank you for your feedback. We hear your comments and as a committer I can
share we are constantly looking to improve the PR process, having already
taken many of the steps you suggest.
However, it is important to notice that the number of PRs should not be
seen as a metric of engagemen
Edgardo,
You are correct that proper handling of pull requests is an important
mechanism for the health of the community, bringing along new
committers, and for adding benefit to the application. We've been
flagging this as an important item to track and focus on in our
quarterly board reports for
Joe - You are correct I was mentioning the PRs that are currently open.
Regardless of how it happens reducing the count of open PRs I believe to be
extremely important. Maybe I was hoping that the release could be a forcing
function to make that happen. I believe that developers are more willing t
Joe, I think you misread. Edgardo is referring to the Pull Requests that are
currently open, not the tickets assigned to the 1.1.0 version.
I think these goals (releasing 1.1.0 and cutting down the PR count) should be
two different efforts. Doing a thorough job reviewing takes a significant
am
There are less than 30 right now. Many of the roughly 90+ JIRAs
opened on 1.1.0 were easily dispositioned to 1.2.0 or closed or just
had fix versions removed.
We will need to have a push over the next bunch of days to deal with
reviewing/merging/moving the remaining items.
Thanks
Joe
On Thu, Oc
Joe,
There are 75 PRs currently open. Why not make a push over the next bunch of
days to get them closed and then cut the release after that.
Cheers,
Edgardo
On Thu, Oct 13, 2016 at 12:44 PM, Joe Witt wrote:
> Team,
>
> There have been a ton of bugs fixed a few nice features. I would like
>
Team,
There have been a ton of bugs fixed a few nice features. I would like
to move to get Apache NiFi 1.1.0 release going pretty much based on
where we are now and plan to move most tickets to a new Apache NiFi
1.2.0 version. We can try to get back on our roughly 6-8 week release
schedule and s
Sounds good Joe. I have no issue to you doing the rm'ing for it.
On Oct 13, 2016 8:19 AM, "Joe Witt" wrote:
> Team,
>
> There are a lot of great fixes and improvements on the master line now
> and we're at a good time window to start pushing for a release. There
> are, however, about 90+ JIRAs
Team,
There are a lot of great fixes and improvements on the master line now
and we're at a good time window to start pushing for a release. There
are, however, about 90+ JIRAs assigned to 1.1.0 which are open. I'm
going to go through them and remove fix versions where appropriate.
I'm happy to
44 matches
Mail list logo