[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172730#comment-14172730
]
Shalin Shekhar Mangar commented on SOLR-6594:
---------------------------------------------
I believe that a simple bulk API can satisfy all requirements for a schema API
and we should no longer attempt to have additional fine-grained end points for
writes. I am not against fine-grained read endpoints but even that can be
satisfied by a bulk API which allows filtering. In future, I wouldn't want to
write/maintain APIs for bulk and individual operations -- I'm assuming a config
API will probably add at least ten fine-grained APIs if we go that way.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
