Yep, that already exists as Bahir. Also, would anyone object to declaring Flume support at least deprecated in 2.4.0? On Wed, Oct 10, 2018 at 2:29 PM Jörn Franke <jornfra...@gmail.com> wrote: > > I think it makes sense to remove it. > If it is not too much effort and the architecture of the flume source is not > considered as too strange one may extract it as a separate project and put it > on github in a dedicated non-supported repository. This would enable > distributors and other companies to continue to use it with minor adaptions > in case their architecture depends on it. Furthermore, if there is a growing > interest then one could pick it up and create a clean connector based on the > current Spark architecture to be available as a dedicated connector or again > in later Spark versions. > > That being said there are also „indirect“ ways to use Flume with Spark (eg > via Kafka), so i believe people would not be affected so much by a removal. > > (Non-Voting just my opinion) > > > Am 10.10.2018 um 22:31 schrieb Sean Owen <sro...@apache.org>: > > > > Marcelo makes an argument that Flume support should be removed in > > 3.0.0 at https://issues.apache.org/jira/browse/SPARK-25598 > > > > I tend to agree. Is there an argument that it needs to be supported, > > and can this move to Bahir if so? > > > > --------------------------------------------------------------------- > > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
--------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
