[
https://issues.apache.org/jira/browse/SOLR-15740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495669#comment-17495669
]
Jason Gerlowski commented on SOLR-15740:
----------------------------------------
I'm starting this out by tackling the schema-read APIs first. I've got a PR
for those here: [https://github.com/apache/solr/pull/577]
Hoping to get to the schema-edit APIs shortly. I think the edit APIs might
need some consideration, since the schema API appears to support "bulk"
operation (i.e. combining multiple commands in the same POST body).
> Rewrite v2 schema APIs using annotation framework
> -------------------------------------------------
>
> Key: SOLR-15740
> URL: https://issues.apache.org/jira/browse/SOLR-15740
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Major
> Labels: V2
>
> Solr's v2 APIs can be implemented in 1 of 2 possible ways: an apispec (i.e.
> JSON file) based approach that was originally conceived when the v2 APIs were
> created, and an approach that relies on annotated POJO objects which has come
> into favor more recently as it results in less duplication and inches our
> APIs ones step towards a more strongly-typed future.
> The consensus has emerged across several JIRAs that the annotated-POJO
> approach is the one that should be used going forward, and that existing v2
> APIs should be cut over as convenient.
> It's worth noting that this will cause the introspection output to lose the
> "description" text for these APIs and their parameters, as there's no support
> for this yet for annotation-based v2 APIs. See SOLR-15117 for more details.
> This ticket aims to tackle this conversion for Solr's schema APIs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
