[
https://issues.apache.org/jira/browse/SOLR-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056179#comment-17056179
]
Cassandra Targett commented on SOLR-14265:
------------------------------------------
I was thinking about this today as I had a moment to pick up SOLR-11646 again
and the first thing I noticed was a Collections API command
(action=CLUSTERSTATUS) which does not have a v2 counterpart.
It made me think that the first thing to do here is possibly an accounting of
what does & doesn't have v2 coverage, get those added, and then work on
removing v1.
> Move to admin API to v2 completely
> -----------------------------------
>
> Key: SOLR-14265
> URL: https://issues.apache.org/jira/browse/SOLR-14265
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
