Github user Leemoonsoo commented on the issue:
    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 
    What do you think?

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 or file a JIRA ticket
with INFRA.

Reply via email to