Seems like one of the proposals (channels) isn't really tied to the
other (supporting more than Spark). I don't really have an opinion on
the latter (other than nobody has shown enough interest to even try to
prototype anything).
For the former, why do you need these separate "channels"? What
diff
Hi guys,
Currently, Livy provides a great "façade" as REST service to interact and deploy
with a Spark cluster.
I wonder if we could not extend this to other "channels" than REST. I'm thinking
about leveraging Apache Camel and others for that (why not interacting with
MQTT/AMQP, ...).
In ter
