Skip to content

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Mar 13, 2025

Hides some of the "extra" lines from ESQL's documentation. These lines are required to make the documentation into nice tests which is important to make sure the docs don't get out of date. But readers don't need to see them.

Hides some of the "extra" lines from ESQL's documentation. These lines
are required to make the documentation into nice tests which is
important to make sure the docs don't get out of date. But readers don't
need to see them.
@nik9000
Copy link
Member Author

nik9000 commented Mar 13, 2025

This is blocked on the ongoing docs rework.

@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) labels Mar 13, 2025
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine
Copy link
Collaborator

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

Copy link
Contributor

@craigtaverner craigtaverner left a comment

Choose a reason for hiding this comment

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

Looks good, but I have two concerns:

  • Is it really necessary. I took a look at the rendered docs, and the extra SORT/LIMIT made the queries look a little more real-world without looking cluttered. Having said that I'm leaning towards doing it your way because these are reference docs and focus on the function at hand seems rational. But I wanted to just double-check this point.
  • This PR does not include any of the generate docs. This has the advantage of being back-portable to 8.x, but the disadvantage of needing an immediate followup PR for both main and 8.x with these rendered docs, otherwise we will see what happened a couple of months ago with a PR unrelated to docs happening to include a bunch of docs stuff just because the developer ran some (or all) unit tests.

My vote is we rebase/squash these commits into one commit, cherry pick that to 8.x, and the make two PRs, one on main (this one) and one on 8.x (new PR) each with all necessary generated files. This PR can then auto-backport to 9.0, and the 8.x version can auto-backport to the versions we care about there.

@nik9000
Copy link
Member Author

nik9000 commented Apr 1, 2025

My vote is we rebase/squash these commits into one commit, cherry pick that to 8.x, and the make two PRs, one on main (this one) and one on 8.x (new PR) each with all necessary generated files. This PR can then auto-backport to 9.0, and the 8.x version can auto-backport to the versions we care about there.

Makes sense to me. I'll squash this one, then regenerate the docs. Then force push. Then make another PR against 8.x.

@nik9000 nik9000 added auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) and removed v8.18.1 v8.19.0 labels Apr 1, 2025
@nik9000 nik9000 enabled auto-merge (squash) April 1, 2025 19:19
@nik9000 nik9000 merged commit d302962 into elastic:main Apr 1, 2025
16 checks passed
@nik9000 nik9000 deleted the esql_move_limit_in_docs branch April 1, 2025 20:24
nik9000 added a commit to nik9000/elasticsearch that referenced this pull request Apr 2, 2025
Hides some of the "extra" lines from ESQL's documentation. These lines
are required to make the documentation into nice tests which is
important to make sure the docs don't get out of date. But readers don't
need to see them.
nik9000 added a commit to nik9000/elasticsearch that referenced this pull request Apr 2, 2025
Hides some of the "extra" lines from ESQL's documentation. These lines
are required to make the documentation into nice tests which is
important to make sure the docs don't get out of date. But readers don't
need to see them.
elasticsearchmachine pushed a commit that referenced this pull request Apr 2, 2025
Hides some of the "extra" lines from ESQL's documentation. These lines
are required to make the documentation into nice tests which is
important to make sure the docs don't get out of date. But readers don't
need to see them.
elasticsearchmachine pushed a commit that referenced this pull request Apr 2, 2025
Hides some of the "extra" lines from ESQL's documentation. These lines
are required to make the documentation into nice tests which is
important to make sure the docs don't get out of date. But readers don't
need to see them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) >docs General docs changes Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Docs Meta label for docs team v9.0.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants