ESQL: Add known issue to 8.15 docs for OOM due to wide index pattern

[alex-spies]

No description provided.

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[alex-spies]

Hey @elastic/es-docs , could you have a look and tell me if I'm doing this correctly? Thanks in advance!

I'm trying to add known issues to the already released versions 8.15.0 and 8.15.1.

I couldn't find release notes for 8.15.1 on main, so I went and added them - is there another place or branch that this should go into instead?

[alex-spies]

I think this needs to go in the 8.15 branch, main doesn't have the 8.15.1 release notes. Closing this in favor of #112930, which is on the 8.15 branch.

[leemthompo]

I think this needs to go in the 8.15 branch, main doesn't have the 8.15.1 release notes. Closing this in favor of #112930, which is on the 8.15 branch.

@alex-spies euggh sorry about that. I just merged the forward porting of 8.15.1 release notes #112568, so really should target the main branch in your PR alright and backport.

[leemthompo]

I had suggested rewording in this comment

[alex-spies]

@leemthompo and @tylerperk , I took over Liam's version (much nicer), added the downgrade option back in, and the suggestion to use a different default view is also in there.

Let me know if you like it this way - if yes, I think this is good to go :)

[leemthompo]

I agree with @nik9000 that downgrading is not easy, and similarly waiting for 8.15.2 isn't ideal. But they are options so I think it makes sense to have them. The others are more practical and quicker to implement.

[tylerperk]

LGTM thanks

[elasticsearchmachine]

💔 Backport failed

Status	Branch	Result
✅	8.15
❌	8.x	Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 112926

[nik9000]

Backported to 8.x with #112959