[
https://issues.apache.org/jira/browse/SOLR-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118391#comment-18118391
]
Jason Gerlowski commented on SOLR-18448:
----------------------------------------
Is it? I swear I recall some recent 'dev@' traffic where you were working on
coming up with a decomposed set of APIs that'd allow us to *not* bring
"CLUSTERSTATUS" to v2 in its current form.
If "CLUSTERSTATUS" is coming to v2 "as is", then I think this can probably be
closed. If we won't have a v2 "CLUSTERSTATUS", then I think there's still
value in this ticket as we have a lot of folks who will continue to use v1
CLUSTERSTATUS via SolrJ and it'd be nice to make that easier for them.
> Create model/POJO types for CLUSTERSTATUS output
> ------------------------------------------------
>
> Key: SOLR-18448
> URL: https://issues.apache.org/jira/browse/SOLR-18448
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: newdev
>
> "CLUSTERSTATUS" is an extremely common v1 API for users writing monitoring
> code, workflows, etc. SolrJ provides
> \{{CollectionAdminRequest.ClusterStatus}} to help users hit this API, but
> doesn't provide much on the response-parsing side. The response class,
> 'CollectionAdminResponse', doesn't offer many helpful 'getters' and largely
> leaves users to write their own \{{NamedList}} inspection code.
> We could make this experience much better for our users by providing a few
> model types or POJOs so that users can use strongly-typed getters instead of
> the null-check and casting-heavy code that's currently required.
> (It might complicate things and require its own ticket, but having some
> strongly-typed model-classes would probably simplify a lot of our server-side
> code that inspects ZK cluster/collection state as well.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
