Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
Are these public-facing, do we need documentation for them too? cc: @hdhalter
In the default installation `GET /_mappings` also currently fails on `.plugins-ml-config` and `.plugins-ml-model`.
Checked some of these boxes after #504.
You cannot evolve a spec in backwards compatible ways across major semver versions because of breaking changes in parameters. For example, imagine an API that takes a field called `name`...
> @wbeckler A client that can talk to any server version is nice but it might be more troublesome than it's worth. It will drastically increase the complexity of the...
With the publishing mechanism in #211 we can publish builds from multiple branches and thus track multiple versions of OpenSearch that aren't compatible.
https://github.com/opensearch-project/opensearch-api-specification/issues/120 is related
I like this minus the "beta" terminology that is not necessary imo. The spec today tests against 2.17 (released) and 3.0 (unreleased). I think we should publish two versions today:...
Let's backup. What are we trying to solve? I think I'm confused. The spec today supports versioning via [OpenAPI extensions](https://github.com/opensearch-project/opensearch-api-specification/blob/main/DEVELOPER_GUIDE.md#openapi-extensions). - `x-version-added`: OpenSearch version when the operation/parameter was added. -...
I think I understand having heard @amberzsy on Slack too. Does publishing a 0.1.0 work? We would publish 0.2.0 when we introduce a breaking change, and 0.1.1 when we don't?