HoustonPutman commented on PR #1115: URL: https://github.com/apache/solr/pull/1115#issuecomment-1305755994
> 1. **Consistency** Most of the proposed v2 APIs are designed around this pattern of `/pluralGroupName/singleInstance` (e.g. `/collections/techproducts`, `/shards/shard1`, `/fields/text`.) The `/commands` path segment helps us stay consistent with that pattern. But given your example (`http://localhost:8983/api/cluster/nodes/localhost:7574_solr/commands/replace/`) the `nodes/SingleNode` is already there, so we are still following this consistency. Maybe the docs in the PR are out of date, but the uniqueness thing is also not an issue because the node name is already in the URL. I understand how the `cores/commands/swap` example makes sense (though it can probably use the same syntax here with `cores/core_name/swap`...), but I think in general its best that we try to leave out `commands` and other filler paths when we can 🙂 -- 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
