You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Eric Pugh (Jira)" <ji...@apache.org> on 2021/01/11 17:22:00 UTC

[jira] [Comment Edited] (SOLR-14265) Move collections admin API to v2 completely

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

David Eric Pugh edited comment on SOLR-14265 at 1/11/21, 5:21 PM:
------------------------------------------------------------------

I just read through the history and now I realize that SOLR-11646 is about that, in terms of documenting those v2 API's for Collections API which is what I'm interested in...!


was (Author: epugh):
I just read through the history and now I realize that SOLR-11646 is about that, in terms of documenting those v2 API's for ConfigSets which is what I'm interested in...!

> Move collections admin API to v2 completely 
> --------------------------------------------
>
>                 Key: SOLR-14265
>                 URL: https://issues.apache.org/jira/browse/SOLR-14265
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Anshum Gupta
>            Assignee: Anshum Gupta
>            Priority: Major
>
> V2 admin API has been available in Solr for a very long time, making it difficult for both users and developers to remember and understand which format to use when. We should move to v2 API completely for all Solr Admin calls for the following reasons:
>  # converge code - there are multiple ways of doing the same thing, there's unwanted back-compat code, and we should get rid of that
>  # POJO all the way - no more NamedList. I know this would have split opinions, but I strongly think we should move in this direction. I created Jira about this specific task in the past and went half way but I think we should just close this one out now.
>  # Automatic documentation
>  # Others
> This is just an umbrella Jira for the task. Let's create sub-tasks and split this up as it would require a bunch of rewriting of the code and it makes a lot of sense to get this out with 9.0 so we don't have to support v1 forever! 
> There have been some conversations going on about this and it feels like most folks are happy to go this route.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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