noblepaul edited a comment on pull request #1730:
URL: https://github.com/apache/lucene-solr/pull/1730#issuecomment-671651150
>what is the target use case of the interface and lazy implementation?
The objectives are many
- The `LazySolrCluster` will be the default impl for these interfaces.
Because, this is the current behaviour (mostly). We expect fresh data to be
available all times
- Totally refactor Solr code base to minimize dependencies on concrete
classes. This enables us to do simulation and testing, make code more readable,
and enable refactoring
- As we move to a new mode for Solr with a lean core and packages/plugins,
we want to have less API surface area against which the plugins are written.
This enables the plugins to work against a wider range of versions without
rewriting/recompiling
The problem with the existing classes implementing the interfaces is that,
users of the APIs will cast these objects to the underlying concrete classes,
which defeats the purpose
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
