Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release notes for elastic/kibana#191730 #1292

Merged

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Sep 5, 2024

This change was originally not intended to be released in 8.15.1, but we are including it at the end.

elastic/kibana#191730

@jsoriano jsoriano self-assigned this Sep 5, 2024
@jsoriano jsoriano requested a review from a team as a code owner September 5, 2024 13:58
Copy link

github-actions bot commented Sep 5, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

Copy link
Contributor

mergify bot commented Sep 5, 2024

This pull request does not have a backport label. Could you fix it @jsoriano? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

Copy link
Member

@kpollich kpollich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth raising this as a known issue or otherwise noteworthy change in addition to including it as a "plain" release note entry? There's some sort of risk with this new behavior, right?

@jsoriano
Copy link
Member Author

jsoriano commented Sep 5, 2024

Added it also as a known issue.

Copy link
Contributor

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@jsoriano jsoriano merged commit 4928797 into elastic:main Sep 5, 2024
3 checks passed
@jsoriano jsoriano deleted the release-notes-fleet-nested-fields-change branch September 5, 2024 15:49
mergify bot pushed a commit that referenced this pull request Sep 5, 2024
jsoriano added a commit to elastic/kibana that referenced this pull request Sep 6, 2024
…emplate (#191730)" (#191897) (#192246)

This change was released at the end in 8.15.1, so let's keep it the
branch.
    
There are definitions of nested objects whose fields are defined as
subfields, like this:
```
  - name: a
    type: nested
    fields:
    - name: b
      type: keyword
```
This should generate a template with the subfields as subproperties:
```
      "properties": {
        ...
        "a": {
          "type": "nested",
          "properties": {
            "b": {
              "ignore_above": 1024,
              "type": "keyword",
            },
          },
        },
      },
```
This change adds support for this. Without it the nested object is
empty, without subfields, what is unexpected.

See elastic/package-spec#784 for more context.

This change was originally reverted in 8.15 in  #191897

Release notes were manually added in elastic/ingest-docs#1292
jsoriano added a commit that referenced this pull request Sep 9, 2024
(cherry picked from commit 4928797)

Co-authored-by: Jaime Soriano Pastor <jsorianopastor@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants