[
https://issues.apache.org/jira/browse/SOLR-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176777#comment-17176777
]
Noble Paul commented on SOLR-14730:
-----------------------------------
This API will live side-by-side with the existing SolrJ APIs.
So, we can commit this to the branch_8x as and when they are ready. There is no
problem in using NamedList in the server.
The deserializing code can deserialize a NamedList into any interface that we
define.
bq.Before starting in earnest, I suggest doing just one API as an example for
peer review before going further.
Totally. This should be 100% peer reviewed before merging in
> Build new SolrJ APIs without concrete classes like NamedList/Map
> ----------------------------------------------------------------
>
> Key: SOLR-14730
> URL: https://issues.apache.org/jira/browse/SOLR-14730
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
> Labels: clean-api
>
> We must minimize weakly typed code. Our public APIs should be programmed
> against interfaces and wherever possible use POJOs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
