[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171108#comment-14171108
]
Steve Rowe commented on SOLR-6594:
----------------------------------
I think it would be very weird from the Schema API consumers' POV to *remove*
existing write access while leaving read access in place for the fine-grained
endpoints.
Also, having separate read- and write-side REST API endpoints seems bad to me.
> deprecate the one action only APIs for schema editing
> -----------------------------------------------------
>
> Key: SOLR-6594
> URL: https://issues.apache.org/jira/browse/SOLR-6594
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
>
> 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 .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
