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

Hoss Man reassigned SOLR-4272:
------------------------------

    Assignee: Hoss Man

Hmmm... the exclusion of RunUpdateProcessor was intentional in order to keep 
the example on point with only what was intentionally being discussed in the 
docs.  but i can see  how it might confuse folks.

I think perhaps the best fix would be to eliminate the 
"<updateRequestProcessorChain>" tags so only the "inner" xml is provided and 
it's clear people should cut/paste into an existing chain (not attempt to use 
as an entire chain)

thoughts?
                
> Documentation for CountFieldValuesUpdateProcessorFactory is missing 
> solr.RunUpdateProcessorFactory in the example
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4272
>                 URL: https://issues.apache.org/jira/browse/SOLR-4272
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 4.0
>            Reporter: Alexandre Rafalovitch
>            Assignee: Hoss Man
>            Priority: Trivial
>             Fix For: 4.1
>
>
> The JavaDoc for CountFieldValuesUpdateProcessorFactory shows a sample 
> processor chain using the processor. 
> However, the example does not finish solr.RunUpdateProcessorFactory which 
> means if somebody copies the example, they may take very long time to see why 
> the updates are not actually happening (speaking from experience here).
> It would be good to update the example to include the extra line (and maybe 
> give the processor name attribute).

--
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

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

Reply via email to