[
https://issues.apache.org/jira/browse/SOLR-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-18278.
---------------------------------
Resolution: Invalid
There appears to be a misunderstanding here. solr-core (where CoreContainer
is) depends on Jetty; this isn't a flaw or requirement we've ever had.
Wish-list: someday maybe, I imagine it'd be interesting if we could split
solr-core up to isolate the EmbeddedSolrServer use-case from the distributed
system that Solr is. If we did that, then I think it'd be a reasonable goal to
have that future solr-core not have a dependency on solrj-jetty or the Jetty
server. If you wish to help make this happen, then I recommend experimentally
detecting where exactly the jetty dependencies lie and we can discuss
mitigations on a case-by-case basis (there will likely be many spots). Maybe
start with a fork hack, and prove it works with an EmbeddedSolrServer test that
works without any Jetty dependency miraculously.
> SOLR JETTY dependency decoupling didn't work properly
> -----------------------------------------------------
>
> Key: SOLR-18278
> URL: https://issues.apache.org/jira/browse/SOLR-18278
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Affects Versions: 10.0
> Reporter: Tharindu Dharmarathna
> Priority: Blocker
>
> WSO2 API Manager going to upgrade the SOLR version into 10.0.0 and trying to
> remove the jetty dependency with SOLR in product.
> During verification we able to found when we initializing CoreContainer it
> have a reference to the Solr-jetty through HttpSolrClientProvider.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
