[
https://issues.apache.org/jira/browse/HADOOP-20008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HADOOP-20008:
------------------------------------
Labels: pull-request-available (was: )
> Give the YARN application catalog its own Jetty version
> -------------------------------------------------------
>
> Key: HADOOP-20008
> URL: https://issues.apache.org/jira/browse/HADOOP-20008
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build, yarn
> Reporter: Jose Luis López
> Priority: Minor
> Labels: pull-request-available
>
> hadoop-yarn-applications-catalog-webapp embeds Solr 8.11.2, which is compiled
> against Jetty 9.4. It needs Jetty even without a container:
> {{EmbeddedSolrServer}}'s constructor loads {{HttpShardHandlerFactory}}, which
> uses the Jetty 9.4 HTTP client. Today that works because Hadoop is on 9.4
> too. Once HADOOP-19972 moves Hadoop to Jetty 12, the two cannot share the
> module's classpath, because they share jetty-http, jetty-io and jetty-util.
> This change decouples the module first, so the upgrade only has to bump
> Hadoop's own version.
> h3. Changes
> * New {{solr.jetty.version}} in the root pom, set to the release trunk ships
> today, 9.4.58.v20250814. Solr 8.11.2 was built against 9.4.44, but nothing
> needs that release.
> * The webapp's pom gets a local {{dependencyManagement}} that overrides the
> inherited {{jetty.version}} pin and imports the jetty-bom of the same
> release. That way all of Solr's Jetty, including solr-core's server side and
> http2, resolves to one 9.4 release.
> h3. Compatibility
> No change: app.war ships the same Jetty as today.
> HADOOP-19998, which moves the catalog off Solr 8, later removes this pin.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
