fix: remove unsupported name field from DerivedField schema#1156
Open
gingeekrishna wants to merge 1 commit into
Open
fix: remove unsupported name field from DerivedField schema#1156gingeekrishna wants to merge 1 commit into
gingeekrishna wants to merge 1 commit into
Conversation
gingeekrishna
requested review from
Tokesh,
VachaShah,
Xtansia,
aabeshov,
harshavamsi,
karenyrx,
lucy66hw and
sachetalva
as code owners
July 5, 2026 14:58
gingeekrishna
pushed a commit
to gingeekrishna/opensearch-java
that referenced
this pull request
Jul 5, 2026
The fix belongs in the OpenSearch API specification, not in generated code. Submitted upstream: opensearch-project/opensearch-api-specification#1156 The java-codegen/opensearch-openapi.yaml change is kept here as a local workaround until the upstream spec fix is pulled in by the weekly code-generation workflow. Signed-off-by: RadhaKrishnan Rajendran <gingeekrishna@gmail.com> Signed-off-by: Radhakrishnan Pachyappan <gingeekrishna@gmail.com>
gingeekrishna
added a commit
to gingeekrishna/opensearch-java
that referenced
this pull request
Jul 5, 2026
The fix belongs in the OpenSearch API specification, not in generated code. Submitted upstream: opensearch-project/opensearch-api-specification#1156 The java-codegen/opensearch-openapi.yaml change is kept here as a local workaround until the upstream spec fix is pulled in by the weekly code-generation workflow. Signed-off-by: RadhaKrishnan Rajendran <gingeekrishna@gmail.com> Signed-off-by: Radhakrishnan Pachyappan <gingeekrishna@gmail.com>
The DerivedField type in _common.yaml declares a 'name' property and marks it as required, but OpenSearch does not recognize this field in mapping definitions. When a client serializes a DerivedField with 'name' set, the server rejects the request with a mapper_parsing_exception: [mapper_parsing_exception] Failed to parse mapping: unknown parameter [name] Remove the 'name' property from DerivedField.properties and from the required list so the schema matches the actual server behavior. Signed-off-by: RadhaKrishnan Rajendran <gingeekrishna@gmail.com> Signed-off-by: Radhakrishnan Pachyappan <radhakrishnan.p@op.tech>
gingeekrishna
force-pushed
the
fix/derivedfield-remove-name-field
branch
from
July 5, 2026 15:07
405e2ee to
a3a2ebe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DerivedFieldinspec/schemas/_common.yamldeclares anameproperty and marks it as required. However, OpenSearch does not recognize this field in mapping definitions. When a client serializes aDerivedFieldwithnameset, the server rejects the request with:This fix removes
namefromDerivedField.propertiesand from therequiredlist so the schema matches the actual server behavior.Fixes #1157
Related
nameparameter opensearch-java#1937Test plan
DerivedFieldserialization no longer includes thenamefieldname