[
https://issues.apache.org/jira/browse/SOLR-16825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774178#comment-17774178
]
ASF subversion and git services commented on SOLR-16825:
--------------------------------------------------------
Commit b74fcaf7ce283aca30ebc85a1498226c3ebfea2d in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b74fcaf7ce2 ]
SOLR-16825: Migrate v2 definitions to 'api' module, pt 6 (#1978)
This commit covers various GET /schema APIss well as delete-shard.
Extracting annotated interfaces for these APIs includes them in the SolrRequest-
generation we now do in SolrJ
> Generate Java bindings from OpenAPI spec
> ----------------------------------------
>
> Key: SOLR-16825
> URL: https://issues.apache.org/jira/browse/SOLR-16825
> Project: Solr
> Issue Type: Improvement
> Components: v2 API
> Reporter: Jason Gerlowski
> Priority: Major
> Time Spent: 12h 10m
> Remaining Estimate: 0h
>
> SOLR-16346 added support to Solr's build to generate an "OpenAPI spec" file
> describing our v2 API. But currently, this spec file isn't actually used by
> Solr in any way.
> Spec files can be used for a variety of purposes, including to [generate
> client bindings|https://github.com/OpenAPITools/openapi-generator] for using
> the API.
> The client generation capabilities provided by the OpenAPI project cover a
> variety of languages, but it make sense for Solr to start with Java since we
> already have a Java client that requires continual effort to keep up to date.
> It'd be a big win for the project if we were able to replace some or all of
> the manually maintained "SolrRequest" implementations in SolrJ with
> automatically generated code.
--
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
