While stale Livy/Spark sessions will be created if they exist, if a Livy session is not present, Jobs will fail immediately without much explanation. Feedback has been that managing Livy sessions is really not something that users want, or should need, to do.
This proposes to have Livy sessions start even if not present, automatically, when code is submitted to Spark.
While stale Livy/Spark sessions will be created if they exist, if a Livy session is not present, Jobs will fail immediately without much explanation. Feedback has been that managing Livy sessions is really not something that users want, or should need, to do.
This proposes to have Livy sessions start even if not present, automatically, when code is submitted to Spark.