gerlowskija commented on PR #2930: URL: https://github.com/apache/solr/pull/2930#issuecomment-2679415513
> It has zero consequences for any caller. It's not really about consequences, it's about being consistent/intuitive. Even users who know about the `PATCH` verb and its semantics will probably reach for `PUT` if they're already used to using it on update-field, and update-config, and update-collprop, and update-configset-file, and update-clusterprop, and update-filestore-entry, and update-clusterprop, and update-noderole, and so on. But like I said - this isn't a hill I'm willing to die on: if anyone else votes for PATCH to tilt the cumulative consensus, or we find another API where it'd work, I'm happy to go that route. In the meantime I'm going to try out the "raw-Map" approach and follow up on SOLR-13271 regarding whether we need to support the arbitrary properties now that we have "Collection Props" as a more formalized thing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
