[
https://issues.apache.org/jira/browse/CONNECTORS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038521#comment-13038521
]
Karl Wright commented on CONNECTORS-19:
---------------------------------------
That's why this ticket was created - to explore using solrj instead of the
homegrown code currently in the connector. However, there are issues we need
to consider before solrj would be an option. The guaranteed delivery problem
is one such. But also if SolrJ spins up its own threads it might well make it
difficult to shut ManifoldCF down properly, depending on how those threads are
created. Just as it is better to use an application server's thread pool when
you are a web application, the same principles apply for threads created by
connectors and their supporting libraries. If you have access to ManifoldCF in
Action, you might want to have a look at chapters 5 and 6 for details.
However, that does not rule solrj out, it just means we need to be cautious if
and when the Solr connector is transitioned to use it. If you want to explore
this in detail by all means feel free - patches are definitely welcome.
> Look into converting SOLR connector to use SolrJ java library
> -------------------------------------------------------------
>
> Key: CONNECTORS-19
> URL: https://issues.apache.org/jira/browse/CONNECTORS-19
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Lucene/SOLR connector
> Reporter: Karl Wright
> Priority: Minor
>
> The SOLR connector currently uses its own multipart post code. It might be a
> good idea to convert it to use the SolrJ client api jar instead. This would
> require license confirmation, plus research to make sure there are no jar
> conflicts as a result, with any other connector.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
