[
https://issues.apache.org/jira/browse/TIKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073017#comment-17073017
]
Konstantin Gribov commented on TIKA-3082:
-----------------------------------------
[~lewismc], my gratitude and big +1 than)
In my experience some OpenAPI/Swagger tools are quite fragile (like
swagger-codegen could break on minor version update) but overall I'm very
inclined to use it since it gives us better maintainability, documentation
generation, easier API versioning.
Also, I'd like to propose moving current APIs to versioned namespace
{{/api/v1/*}} (and redirecting existing methods (like {{/meta}}, {{/rmeta}}
etc) there with HTTP status 301.
BTW, JetBrains IDEA has bundled OpenAPI plugin (at least 2020.1 RC does).
> Consider adding an OpenAPI for tika-server
> ------------------------------------------
>
> Key: TIKA-3082
> URL: https://issues.apache.org/jira/browse/TIKA-3082
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Lewis John McGibbney
> Priority: Major
>
> On TIKA-2253, [~lewismc] asked:
> bq. I was planning on putting together an OpenAPI specification for Tika. Is
> anyone in favor of this?
> What do people think? How much will it change the current tika-server? What
> are the benefits?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
