[
https://issues.apache.org/jira/browse/SOLR-16825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski resolved SOLR-16825.
------------------------------------
Fix Version/s: 9.8
Assignee: Jason Gerlowski
Resolution: Fixed
Alright, I backported the last migration of v2 API definitions from the 'core'
to 'api' modules this morning, so closing this out.
I've marked the "Fix Version" here as 9.8 since that will be the first release
with all of our v2 API definitions migrated over to the 'api' module, though
SolrJ has had at least some auto-generated Java bindings since 9.4.
> 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
> Assignee: Jason Gerlowski
> Priority: Major
> Labels: pull-request-available
> Fix For: 9.8
>
> Time Spent: 13h 50m
> 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
