Thank you all for the responses. @Lior: I have reviewed the change you have mentioned (FLUME-2994). If we manage to have the code done and +1/2-d soon, I'll commit the patch.
@Denes: the change looks good to me. I'll leave some time for others to review, though. @Saikat: I've wanted to put integrations in the User Guide for Flume for so long. For example Flume with Spark ( http://spark.apache.org/docs/latest/streaming-flume-integration.html ). I know it is available on the internet and I don't think we should increase redundancy this way, but I'd really like to have such examples in the docs. What do you all think of this? Misc: any help with the tickets I've mentioned in my last e-mail would be super welcome. (Even just triaging them and maybe deciding if they are not that important as I first thought.) Thank you, Donat On Wed, Oct 5, 2016 at 2:03 AM, Hari Shreedharan <hshreedha...@apache.org> wrote: > +1 for the release, and the branching and RC dates > > On Tue, Oct 4, 2016 at 10:54 AM Saikat Kanjilal <sxk1...@hotmail.com> wrote: > >> Hi Donat, >> >> I can pickup any documentation related issues, are there anymore at this >> point outside of the FLUME-2971, I would be willing to pickup one of the >> ones below but cant guarantee that it'll be fixed in the timeframe for 1.7 >> , let me know the best path for helping. >> >> Thanks >> >> >> ________________________________ >> From: Balazs Donat Bessenyei <bes...@cloudera.com> >> Sent: Tuesday, October 4, 2016 8:01 AM >> To: dev@flume.apache.org >> Subject: Re: [DISCUSS] Flume 1.7 release plan >> >> As there have been no objections, I am going to proceed with the plan >> I have outlined in my original mail. >> >> I will try to work a little more on some flaky tests to help with the >> release process. (Such as FLUME-3002: Some tests in TestBucketWriter >> are flaky.) >> >> It would be awesome if someone could fix FLUME-2971 (Document Kerberos >> set-up for Kafka Sink and Kafka Source). >> >> Also, I have found a few more tickets that could use a little care: >> FLUME-2689 (reloading conf file leads syslogTcpSource not receives any >> event) - probably only needs some more reviews, >> FLUME-2716 (File Channel cannot handle capacity Integer.MAX_VALUE) - >> missing a test, >> FLUME-2461 (memoryChannel bytesRemaining counting error) - missing test >> Patch-less (Needs some investigation and a fix. I am not sure about >> their complexity): >> FLUME-2912 (thrift Sources/Sinks can only authenticate with kerberos >> principal in format with hostname) >> FLUME-2871 (avro sink reset-connection-interval cause >> EventDeliveryException) >> FLUME-2811 (Taildir source doesn't call stop() on graceful shutdown) >> >> However, none of these seem to be a release blocker, so if they are >> not done by Oct 7-10, it would still be fine. >> >> >> Please, let me know your thoughts >> >> Donat >> >> On Mon, Oct 3, 2016 at 3:23 PM, Mike Percy <mpe...@apache.org> wrote: >> > On Fri, Sep 30, 2016 at 7:01 PM, Saikat Kanjilal <sxk1...@hotmail.com> >> > wrote: >> > >> >> I'd be willing to help, I've been heads down on other stuff and have had >> >> to postpone the graph sink implementation (https://issues.apache.org/ >> >> jira/browse/FLUME-2035) but am looking to resume work and targeting an >> >> initial implementation by mid November sometime. In the meantime let me >> >> know how I can get more deeply involved in the next release. >> >> >> > >> > I'd recommend taking a look at things like documentation and filling in >> > gaps so that we don't release with undocumented stuff. Other types of >> > polish seem like a helpful thing to do right before a release as well. >> > >> > Mike >>
