[
https://issues.apache.org/jira/browse/SOLR-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Grama updated SOLR-7182:
-------------------------------
Attachment: SOLR-7182.patch
Created a new version of the patch containing modifications added due to the
newest developments done as part of the resolved Schema API issues (see related
issue links).
> 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, SOLR-7182.patch,
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
