Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19412
I think the argument for it if anything is that it's a) deprecated, so
should kinda be optional to build, and b) this would simply be consistent with
how other external/* modules are handled. For Spark 2.x yes there isn't and
shouldn't be an actual change to the outputs.
There's a legitimate separate question here about whether it should be
deprecated? my sense is yes, to leave the option to remove it in Spark 3.0,
which would probably follow 2.3. I recall something about flume-ng uses an old
version of Netty and it's the thing blocking updating it for all of Spark, but
I may be misremembering the detail there.
Yeah this passed a Maven test build as well as `dev/run-tests` now.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
