Reamer commented on PR #4692: URL: https://github.com/apache/zeppelin/pull/4692#issuecomment-1818462184
> > BTW, with the same reason, we can merge zeppelin-zengine to zeppelin-server. :-) > > Thanks for the information, I have not read through those codes, will take a look after the cleanup work of the interpreters is done. I think it's actually pretty good that we have the two modules (zeppelin-zengine and zeppelin-server). Theoretically, it is possible to replace the application server (currently Jetty). But I don't know anyone who really does that. Nevertheless, it is important to me that we only use standardized configurations and do not rely on deep Jetty functions. But I've already learned about some of the disadvantages. Maybe it makes sense to merge the two modules here. Even if this will certainly not be easy. In principle, I am also thinking of a zeppelin-api module, where there are only interfaces so that you cannot access the class directly in "plugins". -- 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: reviews-unsubscr...@zeppelin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
