Split ESQL functions/operators docs files

[craigtaverner]

▶️ 👁️ URL Preview

Next step in splitting the ES|QL reference documentation for functions and operators into the sub-files needed for generating the docs automatically.

I have a few more actions to take, either in this PR or in a next one:

• Add back generation of sub-files
• Remove intermediate files (ones ending in -new or -orig)

[elasticsearchmachine]

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

[elasticsearchmachine]

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

[leemthompo]

Last four erroring links should be:

logstash://reference/plugins-filters-dissect.md
logstash://reference/plugins-filters-grok.md
beats://docs/reference/index.md
beats://docs/reference/filebeat/filebeat-installation-configuration.md

[craigtaverner]

Last four erroring links should be:

logstash://reference/plugins-filters-dissect.md
logstash://reference/plugins-filters-grok.md
beats://docs/reference/index.md
beats://docs/reference/filebeat/filebeat-installation-configuration.md

OK. I think I've fixed these now.

[leemthompo]

I'd recommend using absolute links to the images folder for simplicity

[leemthompo]

🚗

[elasticsearchmachine]

💔 Backport failed

Status	Branch	Result
❌	9.0	Commit could not be cherrypicked due to conflicts

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

[leemthompo]

there's no need to backport right now because we're only publishing docs from main but we might revisit this strategy going forward

[leemthompo]

💚 All backports created successfully

Status	Branch	Result
✅	9.0

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[kilfoyle]

Hi @leemthompo, @craigtaverner or @colleenmcginnis,

I noticed in this PR that at line 96 of esql-enrich-data.md there are three links to the Beats docs.

You also can set up [{{beats}}](beats://docs/reference/index.md), such as a [{{filebeat}}](beats://docs/reference/filebeat/filebeat-installation-configuration.md), to automatically send and index documents to your source indices. See [Getting started with {{beats}}](beats://docs/reference/index.md).

Corresponding to that, in the Beats Migrate docs from Asciidoc to Markdown PR, the docs build is currently failing with the following errors:

error::e.d.t.d.Log           :: 'elastic/elasticsearch' links to unknown file: 'docs/reference/index.md' in the 'beats' cross link index: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/beats/main/links.json
Error: 'elastic/elasticsearch' links to unknown file: 'docs/reference/index.md' in the 'beats' cross link index: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/beats/main/links.json
error::e.d.t.d.Log           :: 'elastic/elasticsearch' links to unknown file: 'docs/reference/filebeat/filebeat-installation-configuration.md' in the 'beats' cross link index: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/beats/main/links.json
Error: 'elastic/elasticsearch' links to unknown file: 'docs/reference/filebeat/filebeat-installation-configuration.md' in the 'beats' cross link index: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/beats/main/links.json

	The following errors and warnings were found in the documentation

Error: 'elastic/elasticsearch' links to unknown file: 'docs/reference/index.md' in the 'beats' cross link index: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/beats/main/links.json
NOTE: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/beats/main/links.json

Those "unknown" files are present in the Beats PR, but I wonder if the link paths should be like:

[{{beats}}](beats://reference/index.md)

instead of :

[{{beats}}](beats://docs/reference/index.md)

I'm still new to cross-repo linking, so I figured I'd ask first. If any of you can confirm that the change makes sense, I'll open up a PR. Thanks! 🙏

[colleenmcginnis]

Those "unknown" files are present in the Beats PR, but I wonder if the link paths should be like:

[{{beats}}](beats://reference/index.md)

instead of :

[{{beats}}](beats://docs/reference/index.md)

@kilfoyle yep that should do the trick. 🤞

[craigtaverner]

Backport in #124214