[ 
https://issues.apache.org/jira/browse/SOLR-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547261#comment-14547261
 ] 

Marius Grama commented on SOLR-7182:
------------------------------------

I see that this feature request hasn't been updated in a while. I've started 
working on it and implemented the GET methods for the Schema API and will 
continue with the POST methods. 
After having a look at the document 
https://cwiki.apache.org/confluence/display/solr/Schema+API I see that there 
can be exposed also Managed Resources REST API for the Schema API. 
https://cwiki.apache.org/confluence/display/solr/Managed+Resources
Does the Schema API need to support also these features?

> 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: Trunk, 5.2
>
>
> 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]

Reply via email to