[
https://issues.apache.org/jira/browse/SOLR-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583449#comment-14583449
]
Marius Grama commented on SOLR-7182:
------------------------------------
My first intention when writing the Schema API client was indeed to work with
Map<String, Object> type for the parameters. When doing the first tests of the
client I noticed that when dealing with the response I needed to work with
NamedList
e.g. :
{code}
NamedList<Object> fieldProperties = (NamedList<Object>)
fieldResponse.getResponse().get("field");
{code}
which made me use NamedList<Object> for convenience in the request methods.
I will submit shortly a new patch containing Map<String, Object> parameters
instead of NamedList<Object>
> Make the Schema-API a first class citizen of SolrJ
> --------------------------------------------------
>
> Key: SOLR-7182
> URL: https://issues.apache.org/jira/browse/SOLR-7182
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Affects Versions: 5.0
> Environment: any
> Reporter: Sven Windisch
> Priority: Minor
> Labels: api, schema, solrj
> Fix For: 5.2, Trunk
>
> Attachments: SOLR-7182.patch, SOLR-7182.patch
>
>
> There are several Solr APIs that are handled as first class citizens in
> SolrJ, esp. the Node API and the Collections API, i.e. they have their own
> xxxAdminRequest Object extended from the SolrRequest Class. As someone who
> programmatically changes Schemas a lot, I had hoped to see the Schema API
> handled first class in release 5.0, too. As far as I dug into the code and
> docs of SolrJ 5.0, that did not happen. If there is a reasonable point why
> this won't happen at all, I would really like to hear it. If the only reason
> is, that nobody had time for this, I would happily help out here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
