lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uri Boness (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1099) FieldAnalysisRequestHandler
Date Mon, 20 Apr 2009 12:51:47 GMT

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

Uri Boness commented on SOLR-1099:
----------------------------------

Not all input can be sent as input parameters (the documents will still be sent as a request
body via a POST) but of course it's still possible to fold everything in one handler. It just
feels like putting too much logic & responsibility on a single handler which increases
code complexity and makes it harder to maintain (at least in my opinion). The deprecation
also provides users who already use the current ARH a chance to move to the DocumentARH (which
has a different response format)

> 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: AnalisysRequestHandler_refactored.patch, analysis_request_handlers_incl_solrj.patch,
AnalysisRequestHandler_refactored1.patch, 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.


Mime
View raw message