[
https://issues.apache.org/jira/browse/SOLR-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698696#action_12698696
]
Uri Boness commented on SOLR-1099:
----------------------------------
Well, the AnalysisRequestHandler goal is to handle documents, so basically, you
send a XML document (same document as you would send for indexing) and the
handler analyses the fields of the document. So the main difference between the
two handlers is that the AnalsisRequestHandler enables you to provides a set of
field names/types and their values to be analysed, while in the
FieldAnalysisRequestHandler you're mainly targeting just a couple of fields and
you can only specify one value to be analysed. The other main difference is
that the AnalysisRequestHandler handles a POST request with an XML request body
while the FieldAnalysisRequestHandler handles a GET request where all the
parameters are specified as URL params.
As I mentioned, the analysis breakdown of the FieldAnalysisRequestHandler is
more detailed than the AnalysisRequestHandler and this is why I think that some
refactoring can take place by extracting all the common functionality to a
parent class for these two classes.
> FieldAnalysisRequestHandler
> ---------------------------
>
> Key: SOLR-1099
> URL: https://issues.apache.org/jira/browse/SOLR-1099
> Project: Solr
> Issue Type: New Feature
> Components: Analysis
> Affects Versions: 1.3
> Reporter: Uri Boness
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.4
>
> Attachments: FieldAnalysisRequestHandler_incl_test.patch
>
>
> The FieldAnalysisRequestHandler provides the analysis functionality of the
> web admin page as a service. This handler accepts a filetype/fieldname
> parameter and a value and as a response returns a breakdown of the analysis
> process. It is also possible to send a query value which will use the
> configured query analyzer as well as a showmatch parameter which will then
> mark every matched token as a match.
> If this handler is added to the code base, I also recommend to rename the
> current AnalysisRequestHandler to DocumentAnalysisRequestHandler and have
> them both inherit from one AnalysisRequestHandlerBase class which provides
> the common functionality of the analysis breakdown and its translation to
> named lists. This will also enhance the current AnalysisRequestHandler which
> right now is fairly simplistic.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
