manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-981) Solr Connector - classic Solrj SolrInputDocument support
Date Mon, 30 Jun 2014 17:53:24 GMT


Karl Wright commented on CONNECTORS-981:

I have no idea why you are getting no class found errors; you will need
to diagnose that yourself.

The reason I put configuration information in the configuration part of
the UI is because it is related to "how" indexing is done, rather
than "what" is indexed.


Sent from my Windows Phone
From: Alessandro Benedetti (JIRA)
Sent: 6/30/2014 11:35 AM
Subject: [jira] [Commented] (CONNECTORS-981) Solr Connector - classic
Solrj SolrInputDocument support


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

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


This message was sent by Atlassian JIRA

> Solr Connector - classic Solrj SolrInputDocument support
> --------------------------------------------------------
>                 Key: CONNECTORS-981
>                 URL:
>             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

View raw message