Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-6594

deprecate the one action only APIs for schema editing

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.5, 6.0
    • Component/s: None
    • Labels:


      with SOLR-6476 done and committed , we have more than one way of writing to schema . Having two different ways of doing the same thing is counter productive .

      I would like to mark them as deprecated and the calls to those APIs will succeed but will give a deprecation message in the output. The read APIs would continue to be the same , though .

      Details: the following operations have been deprecated as of Solr 5.5, and support for them will be removed in Solr 6.0:

      • Create new field(s): POST to /collection/schema/fields or PUT to /collection/schema/fields/fieldname
      • Create new dynamic field(s): POST to /collection/schema/dynamicfields or PUT to /collection/schema/dynamicfields/glob
      • Create new field type(s): POST to /collection/schema/fieldtypes or PUT to /collection/schema/fieldtypes/name
      • Create new copyField rule(s): POST to /collection/schema/copyfields.

      Note that all of the above operations can instead be performed using the bulk schema API, documented since the 5.0 Solr ref guide here: https://cwiki.apache.org/confluence/display/solr/Schema+API

      To be clear, read-only GET operations on the above-mentioned endpoints will not be changed, deprecated or removed - they will continue to return information about fields, dynamicFields, fieldTypes, and copyField rules, respectively.


        Issue Links



            • Assignee:
              noble.paul Noble Paul


              • Created:

                Issue deployment