[
https://issues.apache.org/jira/browse/SOLR-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796291#action_12796291
]
Andrzej Bialecki commented on SOLR-1602:
-----------------------------------------
I'm in favor of B. This worked well in Hadoop (mapred -> mapreduce) where the
list of deprecations was massive and API changes were not straightforward at
all - still it was done to promote a better design and allow new functionality.
Whole deprecated hierarchies live there for at least two major releases, and
surely they were visible to thousands of Hadoop devs. The downside was
occasional confusion, and of course the porting effort required to use the new
API, but the upside was an excellent back-compat to keep serious users happy,
and a clear message to all to get prepared for the switch.
So IMHO having a bunch of deprecated classes for a while is not a big deal, if
it gives us freedom to pursue a better design.
> 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
> Assignee: Noble Paul
> Fix For: 1.5
>
> Attachments: SOLR-1602.Mattmann.112509.patch.txt,
> SOLR-1602.Mattmann.112509_02.patch.txt, upgrade_solr_config
>
>
> 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.
