[
https://issues.apache.org/jira/browse/SOLR-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617279#comment-17617279
]
Jason Gerlowski commented on SOLR-15749:
----------------------------------------
Anakhe asked a question relating to this ticket over on SOLR-15748; quoting and
replying here to keep all of the discussion around RENAME in one place:
bq. Hello, Jason Gerlowski I'm giving V2_RENAME API its own class on
/solr/handler/API package, as it enables me to work with the templates
provided. is that good to go?
Hmm, we (mostly me, tbh) haven't been nearly as consistent as we should've been
with what package these API classes end up in. Most of the Api classes are
either in {{org.apache.solr.handler.admin.api}} or {{org.apache.solr.handler}},
so I'd recommend one of those packages instead of
{{org.apache.solr.handler.api}} (which looks like it mostly just has some
utility methods?).
> Create a v2 equivalent of v1 'RENAME'
> -------------------------------------
>
> Key: SOLR-15749
> URL: https://issues.apache.org/jira/browse/SOLR-15749
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Major
> Labels: V2
>
> Solr's 'RENAME' command under the v1 \{{/solr/admin/collections}} endpoint
> has no v2 equivalent. This should be remedied to inch v2 closer to parity
> with v1 in preparation for eventual v1 deprecation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
