On Mon, Oct 2, 2017 at 12:34 AM, Nick Pentreath <nick.pentre...@gmail.com> wrote:
> I'd agree with #1 or #2. Deprecation now seems fine. > > Perhaps this should be raised on the user list also? > > And perhaps it makes sense to look at moving the Flume support into Apache > Bahir if there is interest (I've cc'ed Bahir dev list here)? That way the > current state of the connector could keep going for those users who may > need it. > > +1 Apache Bahir main goal is to provide extensions to multiple distributed analytic platforms, extending their reach with a diversity of streaming connectors and SQL data sources. Apache Bahir would welcome proposals to move extensions from Apache Spark to itself, this would give more flexibility to the Spark dev community as they could focus on core functionality, without loosing the ability to enhance these extensions as most of Spark committers have write access to Bahir repositories. Also, users should not see much difference, as Bahir have been creating releases for every Spark release. If the Spark dev community decides to move to this route, please create a jira on the Bahir project and we could use this thread or a new specific one to discuss any details. Thanks -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
