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

Alexandre Rafalovitch commented on SOLR-5896:
---------------------------------------------

My current attempt at the full catalogue is at: 
http://www.solr-start.com/info/update-request-processors/ 

There is a couple of issues I saw when I built it:
  * Fairly deep inheritance hierarchy (which is the main reason this jira 
exists, I guess)
  * Location of non-core URPs to ensure the jars are on the library path (only 
a couple of classes to date)
  * Javadocs, as non-core URPs are not just in different packages, they are in 
different javadoc sets altogether and cannot be discovered when browsing 
Javadoc by parent page
  * Short names (solr.X), also for core- vs. non-core- components

Incidentally, all of the above problems (and a couple more) are even more 
present for the Analyzers, Tokenizers and Filters. That's why I built: 
http://www.solr-start.com/info/analyzers/

Both of the resources above (and several others coming later) and built by 
reverse engineering the production release, looking at the jars and javadocs. 
Basically, brute-forcing the results from the ground-truth as opposed to trying 
to figure out the quirks of the build-system and source-control. 

> Create and edit a CWiki page that describes UpdateRequestProcessors, 
> especially FieldMutatingUpdateProcessors
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5896
>                 URL: https://issues.apache.org/jira/browse/SOLR-5896
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 4.8, 5.0
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>
> The capabilities here aren't really documented as a group anywhere I could 
> see in the official pages, there are a couple of references to them but 
> nothing that really serves draws attention. These need to be documented.
> Where does it make sense to put this? It doesn't really fit under 
> "Understanding Analyzers, Tokenizers, and Filters", except kinda since they 
> can be used to alter how data gets indexed, think of the 
> Parse[Date|Int|Float..] factories.
> Straw-man: add child pages to "Understanding Analyzers, Tokenizers, and 
> Filters" for "What is an UpdateRequestProcessor", "UpdateRequestProcessors", 
> and probably something like "How to configure your UpdateRequestProcessor". 
> Or???



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to