[GitHub] [zeppelin] cuspymd opened a new pull request #4101: [ZEPPELIN-5341] Apply syntax highlight for sample JSON in REST API documents
cuspymd opened a new pull request #4101: URL: https://github.com/apache/zeppelin/pull/4101 ### What is this PR for? Apply syntax highlight for sample JSON in REST API documents ### What type of PR is it? [Documentation] ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-5341 ### How should this be tested? * Checked updated documents locally ### Screenshots (if appropriate) Before  After  ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (ZEPPELIN-5341) Apply syntax highlight for sample JSON in REST API documents
Myoungdo Park created ZEPPELIN-5341: --- Summary: Apply syntax highlight for sample JSON in REST API documents Key: ZEPPELIN-5341 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5341 Project: Zeppelin Issue Type: Improvement Components: documentation Reporter: Myoungdo Park Assignee: Myoungdo Park Attachments: image-2021-04-27-00-52-07-842.png, image-2021-04-27-00-52-34-983.png h4. Before !image-2021-04-27-00-52-07-842.png! h4. After !image-2021-04-27-00-52-34-983.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [zeppelin] asfgit closed pull request #4100: [ZEPPELIN-5336] Inaccurate markdowns in documentations
asfgit closed pull request #4100: URL: https://github.com/apache/zeppelin/pull/4100 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu commented on pull request #4092: [ZEPPELIN-4506] Check for duplicate note on rename of a notebook
zjffdu commented on pull request #4092: URL: https://github.com/apache/zeppelin/pull/4092#issuecomment-826334395 Thanks @dannycranmer will merge it soon -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] asfgit closed pull request #4092: [ZEPPELIN-4506] Check for duplicate note on rename of a notebook
asfgit closed pull request #4092: URL: https://github.com/apache/zeppelin/pull/4092 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu commented on pull request #4097: [ZEPPELIN-5330]. Support conda env for python interpreter in yarn mode
zjffdu commented on pull request #4097: URL: https://github.com/apache/zeppelin/pull/4097#issuecomment-826297779 @Reamer `spark.archives` works, but it is only available after spark 3.1, and I think it is better to put conda env in cloud storage and then specify it via `spark.archives` (because we spark-submit runs in pod so we can not specify local file as `spark.archives`. Do you think whether it work for users ? And I think this PR is orthogonal to `spark.archives`, because `spark.archives` will control both the python environment of driver and executor. The executor is out of control of zeppelin. That's why this approach here only works for python interpreter which zeppelin can control its python environment. But of course we should make the configuration between spark and python interpreter as similar as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu commented on pull request #4100: [ZEPPELIN-5336] Inaccurate markdowns in documentations
zjffdu commented on pull request #4100: URL: https://github.com/apache/zeppelin/pull/4100#issuecomment-826212878 Thanks @cuspymd LGTM -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
