You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Jason Gerlowski (Jira)" <ji...@apache.org> on 2021/10/29 20:20:00 UTC
[jira] [Created] (SOLR-15737) Ensure all (desired) v1 APIs have v2
equivalent
Jason Gerlowski created SOLR-15737:
--------------------------------------
Summary: 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
Security Level: Public (Default Security Level. Issues are Public)
Components: v2 API
Reporter: Jason Gerlowski
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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org