[
https://issues.apache.org/jira/browse/CONNECTORS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038360#comment-13038360
]
Karl Wright commented on CONNECTORS-19:
---------------------------------------
The promised patch never materialized.
One point, though, is that ManifoldCF is not single-threaded in any case, so
you'd be unlikely to gain much in performance by going "multithread" on an
already multi-threaded connector implementation. The current connector can
maintain and use as many connections to Solr as you tell it. Memory buffering
on the client side also is not a good idea because it violates the basic
ManifoldCF principle that you can safely shut down and restart ManifoldCF at
any time without loss.
Solr also suffers from lack of a "guaranteed delivery" metaphor, which I've
talked to the Solr team about in the past. The Solr commit model currently
does not work this way but ManifoldCF really requires it, because without it
there is no way to properly implement an incremental crawler. This would mean
a significant new Solr feature.
> 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
