Skip to content

ZEPPELIN-2083: default interpreter list should honour order of zeppelin.interpreters property in zeppelin-site.xml - #1992

Closed
prabhjyotsingh wants to merge 1 commit into
apache:masterfrom
prabhjyotsingh:ZEPPELIN-2053
Closed

ZEPPELIN-2083: default interpreter list should honour order of zeppelin.interpreters property in zeppelin-site.xml#1992
prabhjyotsingh wants to merge 1 commit into
apache:masterfrom
prabhjyotsingh:ZEPPELIN-2053

Conversation

@prabhjyotsingh

@prabhjyotsinghprabhjyotsingh commented Feb 8, 2017

Copy link
Copy Markdown
Contributor

What is this PR for?

Default interpreter list should honour order of zeppelin.interpreters property in zeppelin-site.xml

What type of PR is it?

[Bug Fix]

What is the Jira issue?

How should this be tested?

Remove default spark interpreter, and and another with a different name say "spark2". This newly created interpreter should show up on top.

Screenshots (if appropriate)

Before:
screen shot 2017-02-08 at 6 58 09 pm

After:
screen shot 2017-02-08 at 6 56 42 pm

Questions:

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

…in.interpreters property in zeppelin-site.xml
@prabhjyotsinghprabhjyotsingh changed the title ZEPPELIN-2053: default interpreter list should honour order of zeppelin.interpreters property in zeppelin-site.xmlZEPPELIN-2083: default interpreter list should honour order of zeppelin.interpreters property in zeppelin-site.xmlFeb 8, 2017
@r-kamath

Copy link
Copy Markdown
Member

Tested, LGTM

@prabhjyotsingh

Copy link
Copy Markdown
ContributorAuthor

@Leemoonsoo can you help review this.

@jongyoul

Copy link
Copy Markdown
Member

LGTM

1 similar comment
@Leemoonsoo

Copy link
Copy Markdown
Member

LGTM

@prabhjyotsingh
prabhjyotsingh deleted the ZEPPELIN-2053 branch February 25, 2018 03:48
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@prabhjyotsingh@r-kamath@jongyoul@Leemoonsoo