[
https://issues.apache.org/jira/browse/SOLR-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-4272.
----------------------------
Resolution: Fixed
Fix Version/s: 5.0
bq. How about ... before and after to indicate that more stuff could be there?
i thought about that, but it seems like that would just get in the way in the
"cut and paste" situation, because it's something that would be in the <pre/>
tags that you'd have to conciously avoid during the "cut" stage.
I cleaned up a bunch of these xml snippet examples to remove the
udpateProcessorChain tags, as well as fixing a bunch that didn't have it to
remove the superfluous trailing newlines.
Committed revision 1430116.
Committed revision 1430118.
> 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, 5.0
>
>
> 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]
