[
https://issues.apache.org/jira/browse/SOLR-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260250#comment-14260250
]
Erik Hatcher commented on SOLR-6895:
------------------------------------
IMO: if we're making this change, existing classes/interfaces need to be
deprecated, not just removed/renamed. Dropping the deprecated stuff can happen
in 6.0, methinks. There's a big *unless*... *unless* there's going to be a
4.10.4 release that deprecates such that we can remove/rename in 5.0. Consider
someone depending on Solr in an automated build by version, but they aren't
going to want to change their indexing code just upgrade to Solr (Server) 5.0,
which would bring in SolrJ 5.0 as well into their builds/compilation perhaps.
> Consider renaming SolrServer to SolrClient
> ------------------------------------------
>
> Key: SOLR-6895
> URL: https://issues.apache.org/jira/browse/SOLR-6895
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Affects Versions: 5.0, Trunk
> Reporter: Alan Woodward
> Priority: Minor
>
> This has been niggling at me for a while. Instantiating a new SolrServer
> object doesn't create a server, it creates a client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
