[
https://issues.apache.org/jira/browse/CONNECTORS-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047756#comment-14047756
]
Alessandro Benedetti commented on CONNECTORS-981:
-------------------------------------------------
A couple of observations :
1) simply replacing the Solr connector jar in my deployment produces :
javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not
initialize class org.apache.http.impl.conn.ManagedHttpClientConnectionFactory
normal ? Am I missing some other component that doesn't allow me to simply
build again only the Solr Connector ?
2) I saw you moved the configuration of the use or not for the Extract update
Handler from the job configuration to the Connector configuration. Of course is
matter of choice, but can you can explain me the advantages of this approach ?
3) after a brief code review it seems ok, by the way
Cheers
> Solr Connector - classic Solrj SolrInputDocument support
> --------------------------------------------------------
>
> Key: CONNECTORS-981
> URL: https://issues.apache.org/jira/browse/CONNECTORS-981
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Lucene/SOLR connector
> Affects Versions: ManifoldCF 1.7
> Reporter: Alessandro Benedetti
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.7
>
> Attachments: CONNECTORS-981.patch
>
>
> The solr connector, according with the development of the Tika Connector
> processor, should be able to operate in 2 ways :
> 1) as usual
> 2) using the classic Solrj SolrInputDocument approach with already extracted
> metadata
> To allow the choice a flag will be added in the UI in the mapping tab ( as
> it's related with how the fields will be processed)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
