[
https://issues.apache.org/jira/browse/CAMEL-21479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21479:
--------------------------------
Fix Version/s: 4.x
> Camel-Solr: Use HttpJdkSolrClient as default SolrClient implementation
> ----------------------------------------------------------------------
>
> Key: CAMEL-21479
> URL: https://issues.apache.org/jira/browse/CAMEL-21479
> Project: Camel
> Issue Type: Improvement
> Components: camel-solr
> Affects Versions: 4.8.1
> Reporter: Paul Blanchaert
> Priority: Minor
> Fix For: 4.x
>
>
> Motivation:
> 1) current solr-component offers many options: 3 endpoints (solr, solrs and
> solrcloud) and the option to provide a solrclient: this is likely confusing
> for non-expert
> 2) many dependencies (o.a. zookeeper) of solr client make it a hard work to
> keep the component up to date and secure
> 3) solr 9.6 introduced a solr client which limits dependencies:
> [HttpJdkSolrClient|https://solr.apache.org/guide/solr/latest/deployment-guide/solrj.html#types-of-solrclients];
> this is a pre-requisite to revive the camel-quarkus-solr component (see
> [quarkus issue|https://github.com/apache/camel-quarkus/issues/6806])
> 4) reducing the options/scope without limiting the user's capabilities will
> allow easier maintenance (in all deploy options of camel)
> Goal:
> 1) update solr-component to reduce to a single endpoint and preferably more
> in line with elastcsearch and opensearch component
> 2) use only the HttpJdkSolrClient per default; this client (new since
> solr-9.6.0) is expected to be sufficient for the supported operations; the
> current solrClient endpoint option will be kept to enable the (experienced)
> user to provide an alternative solrclient implementation
> 3) revive the camel-quarkus-solr component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
