[SOLR-7182] Make the Schema-API a first class citizen of SolrJ

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.0
• Fix Version/s: 5.3, 6.0
• Component/s: SolrJ
• Labels: api schema solrj

Environment

any

• Assignee: Shalin Shekhar Mangar
• Reporter: Sven Windisch
• Created: 02/Mar/15 13:04
• Updated: 02/Oct/19 17:23
• Resolved: 20/Jun/15 16:56

Description

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.

Issue Links

• is related to: SOLR-7679 Schema API doesn't take similarity attribute into account when adding field types
• is related to: SOLR-7682 Schema API - Add New Copy Field Rule doesn't allow maxChars parameter
• is related to: SOLR-7697 Schema API doesn't take class or luceneMatchVersion attributes into account for the analyzer when adding a new field type