From c668cb1cd2c95b31567083e50e3881e83b6b25e8 Mon Sep 17 00:00:00 2001 From: Nik Everett Date: Thu, 3 Oct 2024 11:02:41 -0400 Subject: [PATCH] ESQL: change link to profile explanation Let's use a vendor neutral link. --- docs/reference/esql/esql-query-api.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/esql/esql-query-api.asciidoc b/docs/reference/esql/esql-query-api.asciidoc index 3c8d1f89496ff..d1db21043a5b5 100644 --- a/docs/reference/esql/esql-query-api.asciidoc +++ b/docs/reference/esql/esql-query-api.asciidoc @@ -80,7 +80,7 @@ For syntax, refer to <>. with information about how the query was executed. It provides insight into the performance of each part of the query. This is for human debugging as the object's format might change at any time. Think of this like https://www.postgresql.org/docs/current/sql-explain.html[EXPLAIN ANALYZE] or -https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/EXPLAIN-PLAN.html[EXPLAIN PLAN]. +https://en.wikipedia.org/wiki/Query_plan[EXPLAIN PLAN]. `query`:: (Required, string) {esql} query to run. For syntax, refer to <>. @@ -113,4 +113,4 @@ Values for the search results. Profile describing the execution of the query. Only returned if `profile` was sent in the body. The object itself is for human debugging and can change at any time. Think of this like https://www.postgresql.org/docs/current/sql-explain.html[EXPLAIN ANALYZE] or -https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/EXPLAIN-PLAN.html[EXPLAIN PLAN]. +https://en.wikipedia.org/wiki/Query_plan[EXPLAIN PLAN].