[
https://issues.apache.org/jira/browse/PHOENIX-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531510#comment-17531510
]
Istvan Toth edited comment on PHOENIX-6703 at 5/4/22 6:45 AM:
--------------------------------------------------------------
Partially removing jetty, and shading jetty-util causes the same Minicluster
conflicts that we have now.
When we're running MR jobs, we get those jetty.util classes from the Hadoop
classpath, so I think we're good after all.
was (Author: stoty):
When we're running MR jobs, we get those jetty.util classes from the Hadoop
classpath, so I think we're good after all.
> Exclude Jetty and servlet-api from phoenix-client
> -------------------------------------------------
>
> Key: PHOENIX-6703
> URL: https://issues.apache.org/jira/browse/PHOENIX-6703
> Project: Phoenix
> Issue Type: Improvement
> Components: core
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> phoenix-client-embedded includes a Jetty server, and the Jetty API.
> I don't think that there is a legitimate reason to have a web server in a
> JDBC driver.It adds bloat, and tries to do some stuff at startup which takes
> time.
> More pressingly, the shaded javax.servlet classes conflict with minicluster,
> which breaks the tests in phoenix-queryserver.
> Remove Jetty and the Servlet API from the shaded phoenix-client JAR.
> We could also consider excluding these dependencies in phoenix-core.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
