update paths in SQL files to point to reference content #3270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…om:elastic/docs-content into move-SQL-content-to-Reference-content-docs
…ntent-docs' into move-SQL-content-to-Reference-content-docs
…om:elastic/docs-content into move-SQL-content-to-Reference-content-docs
leemthompo
approved these changes
Oct 3, 2025
…content-to-Reference-content-docs
florent-leborgne
deleted the
move-SQL-content-to-Reference-content-docs
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linked to #2944
This PR retains only a single page for SQL in Explore & Analyze and creates redirects to reference content for all files under Explore & Analyze -> SQL. All files under SQL have been moved to Reference content in another PR: elastic/elasticsearch#135675
The single retained page for SQL will be revamped in another issue: #2945