gerlowskija commented on PR #2930:
URL: https://github.com/apache/solr/pull/2930#issuecomment-2590915285
Ugh, actually, using an HTTP DELETE would conflict with existing paths.
- `DELETE /api/collections/someCollName/properties/somePropName` is my first
choice, but that conflicts with an existing API for deleting
collection-properties.
- `DELETE /api/collections/someCollName/somePropName` was my next thought,
but this also conflicts since "properties" is a valid prop name ("modify"
allows users to specify arbitrary props)
We could come up with some new path-segment to differentiate "modify"
properties from "collection props", say, `DELETE
/api/collections/someCollName/collStateProperties/somePropName`, but that feels
hacky? idk.
Personally, I'm worried the API design issues highlight deeper confusion in
the underlying functionality. Why do we support arbitrary properties in
"modify" that are somehow different from "collectionprops". When would a user
choose to use one or the other? I don't see an answer in our docs, and I don't
know myself 😕 )
--
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
