[
https://issues.apache.org/jira/browse/CAMEL-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340869#comment-17340869
]
Paul Blanchaert commented on CAMEL-16542:
-----------------------------------------
Thanks for this ticket [~acosentino] .
I'd like to list the following specific issues with the camel-solr component
(based on an issue I encountered recently on a camel-solr 3.7.3 implementation):
# Ability to specify the soTimeout and connectionTimeout on "solrCloud" uri in
the same way as they are available on the "solr" uri (using
CloudSolrClient.Builder.withConnectionTimeout, withSocketTimeout); probably
HttpClient and ResponseParser are also good options to add to the builder
(note: the options are 'available' (as in not raising an error) on the
solrCloud endpoint, but are silently ignored and overridden by the standard
Solr client parameters)
# Ability to specify solr parameters (as with
org.apache.camel.component.solr.SolrConstants.PARAM) on the ACTION.COMMIT of
the OPERATION_COMMIT and OPERATION_SOFT_COMMIT: parameters waitFlush and
waitSearcher on the updateRequest.setAction method are currently hard-coded;
but - as with other operations - why not allow to set all parameters via
updateRequest.setParam method; This is applicable to all operations not using
insert method (as the insert method already allows this function for most use
cases)
# Currently, the (default) collection is bound to the solrCloud endpoint; it
should however be possible to specify the collection on exchange level as
exchange header parameter
# Documentation has in general some room for improvement
Let me know when further input/help is useful.
> Camel-Solr: Refactoring the component a bit
> -------------------------------------------
>
> Key: CAMEL-16542
> URL: https://issues.apache.org/jira/browse/CAMEL-16542
> Project: Camel
> Issue Type: Improvement
> Components: camel-solr
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 3.x
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
