[
https://issues.apache.org/jira/browse/SOLR-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124145#comment-18124145
]
Eric Pugh commented on SOLR-15752:
----------------------------------
Fully v1, no v2 equivalent planned:
- Metrics (admin/metrics, wt=prometheus) — Plugins/Stats, cloud node metrics
- Core Info (:core/admin/info) — Core Overview
- Replication (:core/replication) — Replication screen + core overview summary
- Update/Documents (:core/:handler, defaults to update) — Documents screen,
file uploads
- Query (:core/:handler) — Query, Stream, SQL screens (arbitrary handler
forwarding)
- Files (:core/admin/file) — Files/Config Files browser
- Luke (:core/admin/luke) — Schema Browser, Analysis/Documents field pickers
- Analysis (:core/analysis/field) — Analysis screen
v1, kept deliberately pending a v2 gap (code comments explain why):
- Logging setLevel — v2 NodeLoggingApis doesn't yet support the SolrCloud
"nodes=all" broadcast (SOLR-16738)
- Zookeeper clusterState (graph view only — tree browsing already moved to
ZookeeperReadV2) — no v2 equivalent for this particular read
- ZookeeperStatus (admin/zookeeper/status) — ensemble status, no v2 equivalent
- Ping (:core/admin/ping) — enable/disable/ping controls, no v2 equivalent
Hand-rolled $resource, not through a generated V2 client (legacy @EndPoint
handlers predate the OpenAPI v2 framework):
- ParamSet (/api/.../config/params/:name) — v2-shaped URL but no generated
client exists
- Security (/api/cluster/security/:path) — Authentication/Authorization screens
- SchemaDesigner (partial — analyze/query actions only; everything else already
uses SchemaDesignerV2)
- ConfigSetFiles — raw $http.get to a v2 path, not a true v1 holdout, just not
routed through a generated client (needs custom URL encoding/raw-text parsing)
Notably not found: no remaining raw /admin/collections, /admin/cores, or
/solr/<collection>/... calls — those are fully migrated to
CollectionsV2/CoresV2/ClusterV2 already.
> Switch Admin UI to use v2 API
> -----------------------------
>
> Key: SOLR-15752
> URL: https://issues.apache.org/jira/browse/SOLR-15752
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI, v2 API
> Reporter: Jason Gerlowski
> Assignee: Eric Pugh
> Priority: Major
> Labels: V2, pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Having Solr's Admin UI use the v2 API exclusively would be a great way to
> showcase that the v2 API is mature enough to support complex applications.
> Having Solr do this 'dogfooding' will go a long way to building confidence in
> the API and proving it's ready to replace v1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
