Skip to content

Add release notes for 3.6.0#215

Closed
andrross wants to merge 3 commits intomainfrom
release-notes-3.6.0
Closed

Add release notes for 3.6.0#215
andrross wants to merge 3 commits intomainfrom
release-notes-3.6.0

Conversation

@andrross
Copy link
Owner

Description

Release notes for OpenSearch 3.6.0, covering commits from 3.5.0 to HEAD of main (trial run).

Borderline calls

Check List

  • Functionality includes testing.

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

newtonne and others added 3 commits March 20, 2026 19:23
…pensearch-project#20814)

`_field_caps` returns an empty response for indexes where a
`disable_objects: true` object field has been populated with a child
field. A second bug causes such child fields to be corrupted after any
subsequent document is indexed into the same index - for example
`attributes.foo.bar` becomes `attributes.foo.foo.bar`.

## Root causes

When `_field_caps` walks the parent chain of a flattened leaf field
(e.g. `attributes.foo.bar`), it looks up an `ObjectMapper` for each
intermediate path. Under `disable_objects: true`, intermediate paths
like `attributes.foo` have no `ObjectMapper` by design - the fix adds a
null check to skip them and continue up the chain.

The field name corruption is caused by `ParametrizedFieldMapper.merge()`
using `name().lastIndexOf('.')` to reconstruct the parent `ContentPath`
when rebuilding a mapper. For a field with `simpleName` `foo.bar` and
full name `attributes.foo.bar`, this returns the position of the dot
before `bar` rather than the dot before `foo.bar`, so the parent path is
computed as `attributes.foo` instead of `attributes`. The fix computes
the boundary from `simpleName.length()` instead.

Signed-off-by: Cyrus Saeid <cyrus.s.dev@gmail.com>
Co-authored-by: Cyrus Saeid <cyrus.s.dev@gmail.com>
…oject#20951)

Signed-off-by: Marc Handalian <marc.handalian@gmail.com>
Signed-off-by: Andrew Ross <andrross@amazon.com>
@andrross andrross closed this Mar 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants