[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795341#action_12795341
]
Ryan McKinley commented on SOLR-1602:
-------------------------------------
Sounds fine... except for the back compatibility issues -- especially for
people upgrading with the same solrconfig.xml
When we moved all the handlers to a new package o.a.solr.handler, it left a
bunch of deprecated calsses in o.a.solr.request:
{code:java}
@Deprecated
public class StandardRequestHandler extends
org.apache.solr.handler.StandardRequestHandler {
// Don't use this class
}
{code}
Also, if we make a 'response' package, seems SolrQueryResponse.java should go
there.
> Refactor SOLR package structure to include o.a.solr.response and move
> QueryResponseWriters in there
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-1602
> URL: https://issues.apache.org/jira/browse/SOLR-1602
> Project: Solr
> Issue Type: Improvement
> Components: Response Writers
> Affects Versions: 1.2, 1.3, 1.4
> Environment: independent of environment (code structure)
> Reporter: Chris A. Mattmann
> Fix For: 1.5
>
> Attachments: SOLR-1602.Mattmann.112509.patch.txt,
> SOLR-1602.Mattmann.112509_02.patch.txt
>
>
> Currently all o.a.solr.request.QueryResponseWriter implementations are
> curiously located in the o.a.solr.request package. Not only is this package
> getting big (30+ classes), a lot of them are misplaced. There should be a
> first-class o.a.solr.response package, and the response related classes
> should be given a home there. Patch forthcoming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
