I should add that while I made one change that I needed to get the flume configuration from a Spring Cloud Configuration Server I have no plans for any other major changes.
Ralph > On Jan 13, 2022, at 2:23 AM, Apache <ralph.go...@dslextreme.com> wrote: > > Tristan, I am in the process of updating dependencies and applying patches > in prep for a 1.10 release. I hope to have that ready to go within the next > week. > > Ralph > >> On Jan 13, 2022, at 12:31 AM, Tristan Stevens <tris...@apache.org> wrote: >> >> I can confirm from Cloudera’s perspective that Kite is abandoned. >> >> +1 to removing and I think we’re heading towards a Flume 2.0 at this point. >> We can then take things like log4j2, Hive3, Hadoop 3, etc. >> >> Tristan >> >> >> From: Ralph Goers <ralph.go...@dslextreme.com> >> Reply: dev@flume.apache.org <dev@flume.apache.org> >> Date: 12 January 2022 at 17:22:14 >> To: dev@flume.apache.org <dev@flume.apache.org> >> Subject: Re: Flume release that includes the log4j patches. >> >> Given that the Kite Dataset Sink is documented as being experimental and >> since Kite appears to have been abandoned I am making the decisions to >> remove the Kite Dataset Sink from Flume. >> >> Ralph >> >>>> On Jan 12, 2022, at 9:14 AM, Ralph Goers <ralph.go...@dslextreme.com> >>>> wrote: >>> >>> I am working on exactly that. But there are quite a few dependencies that >>> need to be updated besides Log4j. That update was pretty easy. >>> >>> I am currently trying to update the Avro dependency as it also has security >>> issues. Unfortunately, Avro’s upgrade is not completely binary compatible, >>> which is causing an error in the kite-sdk, which appears to be an another >>> Cloudera abandoned project. >>> >>> In short, Apache Flume really needs more people to become active in the >>> project. >>> >>> Ralph >>> >>>>> On Jan 12, 2022, at 6:30 AM, Justin Holmes <jus...@nascency.co.uk> wrote: >>>>> >>>> >>>> Can we have a release that includes the fixed log4j vulnerabilities soon? >>>> >>>> -- >>>> Justin Holmes >>> >>
