[jira] [Commented] (SOLR-15737) Ensure all (desired) v1 APIs have v2 equivalent

["Joshua Ouma (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-15737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614644#comment-17614644 ] 

Joshua Ouma commented on SOLR-15737:
------------------------------------

I would like to work on this issue. Can I be assigned?

> Ensure all (desired) v1 APIs have v2 equivalent
> -----------------------------------------------
>
>                 Key: SOLR-15737
>                 URL: https://issues.apache.org/jira/browse/SOLR-15737
>             Project: Solr
>          Issue Type: Improvement
>          Components: v2 API
>            Reporter: Jason Gerlowski
>            Priority: Major
>              Labels: V2, newdev
>
> Nothing in Solr's build system enforced consistency across v1<->v2, so as a result today, many v1 APIs (or API sub-commands) have no v2 counterpart. In some rare cases this was intentional (e.g. \{{/solr/admin/collections?action=MIGRATESTATEFORMAT}} ), but in most cases it's the result of unintentional omission.
> This ticket aims to remedying this, by finding v1 APIs without a v2 counterpart and adding them where desired.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org