gerlowskija commented on PR #3299:
URL: https://github.com/apache/solr/pull/3299#issuecomment-2775490954
Alright, the JAX-RS code is in place so I've marked this as "Ready for
Review".
One thing that I've left out of this PR, that we'll want to think through
and handle separately are v2 APIs for "copy-field" modification. All of our
other schema entities (fields, field-types, and dynamic-fields) have names that
allow you to address them with nice clean resource-based paths like `PUT or
DELETE /collections/<collName>/schema/fields/<fieldName>`. But copy-fields
break this pattern.
I wasn't sure how to handle them, so I've "punted" in this PR. The best
approach I can think of currently is a `POST /schema/copyfields {...}`, but it
deserves some more thought/discussion.
--
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
