lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1099) FieldAnalysisRequestHandler
Date Tue, 21 Apr 2009 07:43:47 GMT

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

Shalin Shekhar Mangar updated SOLR-1099:
----------------------------------------

    Attachment: SOLR-1099.patch

Patch with the following changes:
# Removed rsp.getResponseHeader().add("params", req.getParams().toNamedList()); from AnalysisRequestHandlerBase
as that is already done in SolrCore#execute if echoParams=explicit is passed as a request
param (or configured in solrconfig.xml)
# Re-formatted code to Lucene/Solr code style
# Added /analysis/document and /analysis/field to example solrconfig.xml with documentation
and added a note on the deprecation of AnalysisRequestHandler

All tests pass.

Uri, AnalysisRequest cannot be an inner class of FieldAnalysisRequestHandler because when
people use Solrj, FieldAnalysisRequestHandler won't be in the class-path. Same for DocumentAnalysisRequestHandler.
We'd need to change this.

> 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, SOLR-1099.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