[
https://issues.apache.org/jira/browse/SOLR-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260182#comment-14260182
]
Yonik Seeley commented on SOLR-6895:
------------------------------------
bq. I think if we're going over a major version change (4 -> 5), we don't need
to worry about binary compatibility here?
I'm primarily talking about compatibility with clients which have SolrJ
embedded.
But we should also consider how to make migration easy for those clients to
upgrade their code as well... SolrJ (being the primary Java client) is sort of
different than other parts of Solr (where reliance on Java interfaces is always
expert level).
> 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]
