Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Draft] [ZEPPELIN-5703] Support to run another notebook in notebook inline #4339

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zjffdu
Copy link
Contributor

@zjffdu zjffdu commented Apr 2, 2022

What is this PR for?

A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html

What type of PR is it?

[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]

Todos

  • - Task

What is the Jira issue?

How should this be tested?

  • Strongly recommended: add automated unit tests for any new or changed behavior
  • Outline any manual steps to test the PR here.

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update?
  • Is there breaking changes for older versions?
  • Does this needs documentation?

@zjffdu zjffdu force-pushed the ZEPPELIN-5703 branch 3 times, most recently from 16861c8 to d0f8ea9 Compare April 3, 2022 06:04
@jongyoul jongyoul changed the title [DRAFR] [ZEPPELIN-5703] Support to run another notebook in notebook inline [DRAFT] [ZEPPELIN-5703] Support to run another notebook in notebook inline Apr 4, 2022
@zjffdu zjffdu changed the title [DRAFT] [ZEPPELIN-5703] Support to run another notebook in notebook inline [Draft] [ZEPPELIN-5703] Support to run another notebook in notebook inline Apr 8, 2022
@@ -975,6 +975,9 @@ public void restart(String settingId, String user, String noteId) throws Interpr

// restart in note page
public void restart(String settingId, ExecutionContext executionContext) throws InterpreterException {
if (settingId == null || settingId.startsWith("__internal__")) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about adding comment to describe __internal__?

Suggested change
if (settingId == null || settingId.startsWith("__internal__")) {
// __internal__ is set by RunNotebookInterpreter
if (settingId == null || settingId.startsWith("__internal__")) {

import org.apache.zeppelin.interpreter.InterpreterSetting;
import org.apache.zeppelin.interpreter.InterpreterSettingManager;
import org.apache.zeppelin.interpreter.ManagedInterpreterGroup;
import org.apache.zeppelin.interpreter.*;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the current style rule but might be replaced by IDE automatically?

}

@VisibleForTesting
public static Map<String, String> parseParams(String text) throws InvalidParameterFormatException {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious. Why don't we use regex to handle it? It also handle some exceptional cases but I wonder if we need to handle that case or not.

jongyoul
jongyoul previously approved these changes Apr 14, 2022
Copy link
Member

@jongyoul jongyoul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM except for some trivial comments.

@jongyoul
Copy link
Member

@zjffdu PR itself looks good to me but I have a question about this idea itself. We had a plan to provide job manager which handle DAG for paragraphs but it's not proceeded well. You PR looks a different way to handle a similar request. Then, can we remote job manager on Zeppelin? It shows some status but it's not that helpful even the quest is too complicated. WDYT?

@zjffdu zjffdu force-pushed the ZEPPELIN-5703 branch 3 times, most recently from 838fc18 to c992c60 Compare April 22, 2022 01:54
@zjffdu zjffdu force-pushed the ZEPPELIN-5703 branch 2 times, most recently from d6a424f to bbbfcb4 Compare April 22, 2022 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants