Expose livy endpoint management through wrapper kernel about sparkmagic HOT 5 CLOSED

• %info will list the sessions for the livy endpoint that notebook is running against.
• %delete -f session_id will delete a session for the livy endpoint that notebook is running against by its id. Without the -f, an error will be displayed telling user that running Spark context might be affected.
• %cleanup -f will delete all sessions for the livy endpoint that notebook is running against. Without the -f, an error will be displayed telling user that running Spark context might be affected.

@msftristew

from sparkmagic.

So the -f argument is always required for the %delete call? That seems wrong.

from sparkmagic.

Always required for delete and cleanup, since they are destructive operations and we want users to understand that.

from sparkmagic.

I don't think I agree with that design decision. %delete and %cleanup are obviously destructive operations by their names.

from sparkmagic.

From the running notebook, you could issue a cleanup which would delete all sessions, including the one created for the running kernel wrapper. That's the rationale behind the -f.

We want the customer to be conscious of this behavior, much like other command tools and etc force you to provide -f before proceeding.

from sparkmagic.