[GitHub] [zeppelin] zjffdu commented on pull request #4508: Bump ivy from 2.4.0 to 2.5.1 in /flink/flink-scala-parent
zjffdu commented on PR #4508: URL: https://github.com/apache/zeppelin/pull/4508#issuecomment-1598025256 I think it is not used any more, can be removed. -- 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. To unsubscribe, e-mail: dev-unsubscr...@zeppelin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] Reamer commented on pull request #4621: [ZEPPELIN-5933] Polish jetty
Reamer commented on PR #4621: URL: https://github.com/apache/zeppelin/pull/4621#issuecomment-1597553878 Hi @joakime I hope you are still active in the Jetty project and wanted to take this opportunity to thank you for your detailed https://github.com/eclipse/jetty.project/issues/6592#issuecomment-897877018. I would be very grateful if you also share your opinion on the pull request. -- 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. To unsubscribe, e-mail: dev-unsubscr...@zeppelin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] Reamer opened a new pull request, #4621: [ZEPPELIN-5933] Polish jetty
Reamer opened a new pull request, #4621:
URL: https://github.com/apache/zeppelin/pull/4621
### What is this PR for?
This PR addresses all comments from the following comment.
https://github.com/eclipse/jetty.project/issues/6592#issuecomment-897877018
The comments were very helpful to do a better configuration in the code.
Especially `server.setDumpAfterStart(true);` helped to get a good overview.
Since the dump is quite long and only helpful for debugging, I added it
temporarily during development. However, due to its great usefulness, the
command should not go unmentioned.
During development, I made sure that we did not use any special Jersey
functions to simplify possible portability.
```
packages("org.apache.zeppelin.rest");
```
Since I forgot to include the Session API during development, I added a
simple test class.
Please note that we currently expose the API and various other endpoints
(e.g. Prometheus, Ping, Health) on two endpoints with appropriate configuration.
For the API endpoint once under `/api/` and once under `/next/api/`.
I don't think this will cause any problems.
### What type of PR is it?
* Improvement
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-5933
### How should this be tested?
* CI
### Questions:
* Does the license files need to 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.
To unsubscribe, e-mail: dev-unsubscr...@zeppelin.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (ZEPPELIN-5933) Polish Jetty configuration
Philipp Dallig created ZEPPELIN-5933: Summary: Polish Jetty configuration Key: ZEPPELIN-5933 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5933 Project: Zeppelin Issue Type: Bug Components: zeppelin-server Affects Versions: 0.10.1 Reporter: Philipp Dallig Assignee: Philipp Dallig Referring to the following comment, we should improve some Jetty configurations in our current setup and polish the configuration. https://github.com/eclipse/jetty.project/issues/6592#issuecomment-897877018 -- This message was sent by Atlassian Jira (v8.20.10#820010)
