[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691284#comment-17691284
]
Jason Gerlowski commented on SOLR-13942:
----------------------------------------
The scarcity of JS familiarity in the community is a real problem for sure - I
don't think _any_ of us feel comfortable with it. But OTOH not addressing
these things as they come up isn't sustainable either. And I say that as
someone who's also guilty of doing it.
I'm as scared of JS as the next person, but maybe small JS edits aren't as
impossible as we tend to treat them. Most of these API related things in the
Admin UI live in services.js afaict, and seem at least mostly-comprehensible.
(See the {{/admin/zookeeper}} code
[here|https://github.com/apache/solr/blob/main/solr/webapp/web/js/angular/services.js#L72]
as an example.)
But maybe I'm missing something: what do you mean by "non-standard APIs"
[~noble.paul]? Is there some wrinkle here that makes the /admin/zookeeper API
particularly hard to migrate off of? It seems like most of the information it
exposes is covered by the additional ZK endpoints you added in this ticket?
> /api/cluster/zk/* to fetch raw ZK data
> --------------------------------------
>
> Key: SOLR-13942
> URL: https://issues.apache.org/jira/browse/SOLR-13942
> Project: Solr
> Issue Type: New Feature
> Components: v2 API
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Minor
> Fix For: 8.6
>
> Time Spent: 8h 40m
> Remaining Estimate: 0h
>
> example
> download the {{state.json}} of
> {code}
> GET http://localhost:8983/api/cluster/zk/collections/gettingstarted/state.json
> {code}
> get a list of all children under {{/live_nodes}}
> {code}
> GET http://localhost:8983/api/cluster/zk/live_nodes
> {code}
> If the requested path is a node with children show the list of child nodes
> and their meta data
--
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
