[ https://issues.apache.org/jira/browse/SOLR-15737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617846#comment-17617846 ]
Joshua Ouma commented on SOLR-15737: ------------------------------------ API inputs and outputs are specified differently in the JAX-RS framework. Where methods in the old v2 framework could either take a SolrQueryRequest/SolrQueryResponse pair, or a Payload>, JAX-RS API methods can have flexible signatures, with a method argument for each query-parameter, path-parameter, etc. Additionally, in JAX-RS, API methods can have a non-void return value to indicate the response back to the user. {quote}(See here for an example).{quote} Example link is not included > 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-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org