[ https://issues.apache.org/jira/browse/SOLR-15737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713319#comment-17713319 ]
ASF subversion and git services commented on SOLR-15737: -------------------------------------------------------- Commit 8638b8a1134521c1ec36456211f148f4cdb083d9 in solr's branch refs/heads/main from John Durham [ https://gitbox.apache.org/repos/asf?p=solr.git;h=8638b8a1134 ] SOLR-15737: Add v2 equivalent of collection "snapshot" APIs (#1471) Snapshots can now be created or deleted at `/api/collections/collName/snapshots/snapshotName` (`POST` and `DELETE` respectively), and listed at `GET /api/collections/collName/snapshots`. --------- Co-authored-by: Jason Gerlowski <gerlowsk...@apache.org> > 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 > Time Spent: 4h > Remaining Estimate: 0h > > 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-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org