You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Erik Faessler (JIRA)" <de...@uima.apache.org> on 2013/07/22 14:54:48 UTC

[jira] [Created] (UIMA-3096) A LuCas extension that allows ro index the Lucene documents created by LuCas into a Solr server.

Erik Faessler created UIMA-3096:
-----------------------------------

             Summary: A LuCas extension that allows ro index the Lucene documents created by LuCas into a Solr server.
                 Key: UIMA-3096
                 URL: https://issues.apache.org/jira/browse/UIMA-3096
             Project: UIMA
          Issue Type: Improvement
          Components: Sandbox-Lucas
    Affects Versions: 2.3.1Addons
            Reporter: Erik Faessler
            Priority: Minor


Add a UIMA component extending LuceneDocumentAE that converts the Lucene document instances created by LuCas into Solr's PreAnalyzed field format (http://wiki.apache.org/solr/PreAnalyzedField). The converted documents are then sent in batches to Solr using the SolrJ API.
On the Solr side, PreAnalyzedUpdateProcessorFactory (http://lucene.apache.org/solr/4_3_1/solr-core/org/apache/solr/update/processor/FieldMutatingUpdateProcessorFactory.html) can be used to restrict the pre-analyzed field values to an existing Solr schema. In case that the LuCas mapping file matches the Solr schema, it is easy as this:
In solrconfig.xml, add this updateRequestProcessorChain:

 <updateRequestProcessorChain name="pre-analyzed-json">
    <processor class="solr.PreAnalyzedUpdateProcessorFactory">
      <str name="fieldRegex">.*</str>
      <str name="parser">json</str>
    </processor>
    <processor class="solr.RunUpdateProcessorFactory" />
  </updateRequestProcessorChain>

Then, add this chain to the default update handler:

<requestHandler name="/update" class="solr.UpdateRequestHandler">
       <lst name="defaults">
         <str name="update.chain">pre-analyzed-json</str>
       </lst>
  </requestHandler>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira