LGTM 👍

LGTM 👍 👍

In case users who already have conf/interpreter.json upgrades Zeppelin, the file includes old classname. for example

  "interpreterSettings": {
    "2BUVF72FJ": {
      "id": "2BUVF72FJ",
      "name": "md",
      "group": "md",
      "interpreterGroup": [
        {
          "name": "md",
          "class": "org.apache.zeppelin.markdown.Markdown",
          "defaultInterpreter": false
        }
      ],

Will there be any problem because of classname change in this case?
Should we change MarkdownInterpreter to Markdown? or Markdown to MarkdownInterpreter?

What do you think?

@Leemoonsoo Thank you for pointing it out. I think changing the class name to Markdown is more proper way to avoid compatibility issue.

Merging if there is no more discussion

I am facing issues in my local on running paragraph with md interpreter since the markdown class name is 'MarkdownInterpreter' in conf/interpreter.json What should I do to resolve this without deleting the interpreter.json file?

Thanks,
Kavin
MailTo: [email protected]

@kavinkumarks I think you can stop Zeppelin and replace all "org.apache.zeppelin.markdown.MarkdownInterpreter" to "org.apache.zeppelin.markdown.Markdown" in conf/interpreter.json, and then start Zeppelin.

@Leemoonsoo Yeah, it worked by changing it manually.I thought that it should have been taken care auto* when someone changes the relevant class name in the appropriate interpreter-setting.json What do you say?

Thanks,
Kavin
MailTo: [email protected]

@kavinkumarks Yep. class name shouldn't be changed. 'MarkdownInterpreter' to 'Markdown' name change didn't happened across different versions of release. Otherwise, yes, will be taken care automatically.

Thanks @Leemoonsoo !

-Kavin