[ 
https://issues.apache.org/jira/browse/SOLR-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man resolved SOLR-5254.
----------------------------
       Resolution: Fixed
    Fix Version/s: 5.2

I think we're pretty much good to go here - i've made some tweaks and moved the 
page under the solrconfig.xml section for the 5.2 guide.

(there's still a lot of cross linking that can be done between this page and 
various sections of the doc where some of the specific update processors are 
useful, but that's true for a lot of things in the doc.)

> 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
>             Fix For: 5.2
>
>
> 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