Github user gss2002 commented on the issue: https://github.com/apache/zeppelin/pull/1447 @spektom I think what happens here is this code fires.. which has nothing to do with the fix here.. in LivySparkInterpreter: return livyHelper.interpretInput(line, interpreterContext, userSessionMap, out, sessionId2AppIdMap.get(sessionId), sessionId2WebUIMap.get(sessionId), displayAppInfo); That gets called before the NoSessionException occurs.. And then in LivyHelper --> public InterpreterResult interpretInput grabs the exception and handles it. I guess the question is can we do a rootcause on this and rethrow? } catch (Exception e) { LOGGER.error("error in interpretInput", e); return new InterpreterResult(Code.ERROR, e.getMessage()); }
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---