[ 
https://issues.apache.org/jira/browse/SOLR-16825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897692#comment-17897692
 ] 

ASF subversion and git services commented on SOLR-16825:
--------------------------------------------------------

Commit eef9bbca1326024ddf9b081597ff7ebc33159dfa in solr's branch 
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=eef9bbca132 ]

SOLR-16825: Migrate v2 API definitions to 'api' module, pt 8 (#2833)

SOLR-16825 added a new gradle module, 'api', which holds v2 API
definitions as interfaces.  This allows us to generate an OAS (and other
artifacts) as a part of the solrj build.  But these artifacts only cover
the v2 APIs present in the 'api' module.

This commit moves v2 API defining annotations to new interfaces in the
'api' module for several "schema", "replication", and "logging" APIs as
well as 'create-alias'.  This APIs are all now reflected in our OAS and
generated artifacts.

> 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
>              Labels: pull-request-available
>          Time Spent: 13.5h
>  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

Reply via email to