[ 
https://issues.apache.org/jira/browse/SOLR-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118306#comment-14118306
 ] 

Hoss Man commented on SOLR-5254:
--------------------------------

aparently we've had a dup of this issue for quite a while: SOLR-5896

ErickE just resolved SOLR-5896 after adding a basic page listing all of hte 
UpdateProcessors -- but i think there's still a fair bit of work to do: for 
starters there's stll not real explanation of what the heck and update 
processor is, let alone what an update processor chain is -- how to configure, 
how to select a chain at runtime, etc....

> ref guide needs page/section on update processor chains
> -------------------------------------------------------
>
>                 Key: SOLR-5254
>                 URL: https://issues.apache.org/jira/browse/SOLR-5254
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Hoss Man
>            Priority: Minor
>
> update processor chans have never really been explained in the ref guide, 
> just mentioned little bits here and there in the context of functionality 
> that uses/depend on a spcitic update processor.
> we should probably have a cohesive page (under 
> https://cwiki.apache.org/confluence/display/solr/Indexing+and+Basic+Data+Operations
>  i would think) introducing hte concept and mentioning some of the "general" 
> update processors (ie: the field mutators, the UUIDUpdateProcessor, etc...), 
> and then back link to it for an explanation from some of hte other pages 
> where processors are mentioned...
> * https://cwiki.apache.org/confluence/display/solr/UIMA+Integration
> * 
> https://cwiki.apache.org/confluence/display/solr/Detecting+Languages+During+Indexing
> * https://cwiki.apache.org/confluence/display/solr/De-Duplication
> etc...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to