ADD EN version of SELECT (#6090)

Co-authored-by: Ivan Blinkov <ivan@ydb.tech>

Author: Pseudolukian

ydb/docs/en/core/_includes/not_allow_for_olap_note.md

@@ -0,0 +1,9 @@
+{% if backend_name == "YDB" %}
+
+{% note warning %}
+
+{% include [OLAP_not_allow_text](not_allow_for_olap_text.md) %}
+
+{% endnote %}
+
+{% endif %}

ydb/docs/en/core/_includes/not_allow_for_olap_text.md

@@ -0,0 +1 @@
+Supported only for [row-oriented](../concepts/datamodel/table.md#row-oriented-tables) tables. Support for [column-oriented](../concepts/datamodel/table.md#column-oriented-tables) tables is currently under development.

ydb/docs/en/core/dev/example-app/_includes/steps/04_query_processing.md

@@ -1,4 +1,4 @@
 ## Retrieving data with a Select {#query-processing}
 
-Retrieving data using a [`SELECT`](../../../../yql/reference/syntax/select.md) statement in [YQL](../../../../yql/reference/index.md). Handling the retrieved data selection in the app.
+Retrieving data using a [`SELECT`](../../../../yql/reference/syntax/select/index.md) statement in [YQL](../../../../yql/reference/index.md). Handling the retrieved data selection in the app.
 

ydb/docs/en/core/dev/yql-tutorial/select_all_columns.md

@@ -1,6 +1,6 @@
 # Selecting data from all columns
 
-Select all columns from the table using [SELECT](../../yql/reference/syntax/select.md):
+Select all columns from the table using [SELECT](../../yql/reference/syntax/select/index.md):
 
 {% include [yql-reference-prerequisites](_includes/yql_tutorial_prerequisites.md) %}
 

ydb/docs/en/core/yql/reference/yql-core/builtins/_includes/basic/evaluate_expr_atom.md

@@ -1,6 +1,6 @@
 ## EvaluateExpr, EvaluateAtom {#evaluate_expr_atom}
 
-Evaluate an expression before the start of the main calculation and input its result to the query as a literal (constant). In many contexts, where only a constant would be expected in standard SQL (for example, in table names, in the number of rows in [LIMIT](../../../syntax/select.md#limit), and so on), this functionality is implicitly enabled automatically.
+Evaluate an expression before the start of the main calculation and input its result to the query as a literal (constant). In many contexts, where only a constant would be expected in standard SQL (for example, in table names, in the number of rows in [LIMIT](../../../syntax/select/limit_offset.md), and so on), this functionality is implicitly enabled automatically.
 
 EvaluateExpr can be used where the grammar already expects an expression. For example, you can use it to:
 

ydb/docs/en/core/yql/reference/yql-core/syntax/_includes/commit.md

@@ -0,0 +1 @@
+{% include [x](_includes/select/commit.md) %}

ydb/docs/en/core/yql/reference/yql-core/syntax/_includes/discard.md

@@ -1,6 +1,6 @@
 # DISCARD
 
-Calculates {% if select_command == "SELECT STREAM" %}[`SELECT STREAM`](../select_stream.md){% else %}[`SELECT`](../select.md){% endif %}{% if feature_mapreduce %}{% if reduce_command %}, [`{{ reduce_command }}`](../reduce.md){% endif %}, or [`{{ process_command }}`](../process.md){% endif %} without returning the result neither to the client or table. {% if feature_mapreduce %}You can't use it along with [INTO RESULT](../into_result.md).{% endif %}
+Calculates {% if select_command == "SELECT STREAM" %}[`SELECT STREAM`](../select_stream.md){% else %}[`SELECT`](../select/index.md){% endif %}{% if feature_mapreduce %}{% if reduce_command %}, [`{{ reduce_command }}`](../reduce.md){% endif %}, or [`{{ process_command }}`](../process.md){% endif %} without returning the result neither to the client or table. {% if feature_mapreduce %}You can't use it along with [INTO RESULT](../into_result.md).{% endif %}
 
 It's good to combine it with [`Ensure`](../../builtins/basic.md#ensure) to check the final calculation result against the user's criteria.
 

ydb/docs/en/core/yql/reference/yql-core/syntax/_includes/expressions/lambda.md

@@ -6,7 +6,7 @@ List arguments in round brackets, following them by the arrow and lambda functio
 
 The scope for the lambda body: first the local named expressions, then arguments, then named expressions defined above by the lambda function at the top level of the query.
 
-Only use pure expressions inside the lambda body (those might also be other lambdas, possibly passed through arguments). However, you can't use [SELECT](../../select.md), [INSERT INTO](../../insert_into.md), or other top-level expressions.
+Only use pure expressions inside the lambda body (those might also be other lambdas, possibly passed through arguments). However, you can't use [SELECT](../../select/index.md), [INSERT INTO](../../insert_into.md), or other top-level expressions.
 
 One or more of the last lambda parameters can be marked with a question mark as optional: if they haven't been specified when calling lambda, they are assigned the `NULL` value.
 

ydb/docs/en/core/yql/reference/yql-core/syntax/_includes/expressions/tables.md

@@ -10,9 +10,9 @@ A table expression is an expression that returns a table. Table expressions in Y
 
 Semantics of a table expression depends on the context where it is used. In YQL, table expressions can be used in the following contexts:
 
-* Table context: after [FROM](../../select.md#from).
+* Table context: after [FROM](../../select/from.md).
 In this case, table expressions work as expected: for example, `$input = SELECT a, b, c FROM T; SELECT * FROM $input` returns a table with three columns.
-The table context also occurs after [UNION ALL](../../select.md#unionall){% if feature_join %}, [JOIN](../../join.md#join){% endif %}{% if feature_mapreduce and process_command == "PROCESS" %}, [PROCESS](../../process.md#process), [REDUCE](../../reduce.md#reduce){% endif %};
+The table context also occurs after [UNION ALL](../../select/union.md#unionall){% if feature_join %}, [JOIN](../../join.md#join){% endif %}{% if feature_mapreduce and process_command == "PROCESS" %}, [PROCESS](../../process.md#process), [REDUCE](../../reduce.md#reduce){% endif %};
 * Vector context: after [IN](#in). In this context, the table expression must contain exactly one column (the name of this column doesn't affect the expression result in any way).
 A table expression in a vector context is typed as a list (the type of the list element is the same as the column type in this case). Example: `SELECT * FROM T WHERE key IN (SELECT k FROM T1)`;
 * A scalar context arises _in all the other cases_. As in a vector context, a table expression must contain exactly one column, but the value of the table expression is a scalar, that is, an arbitrarily selected value of this column (if no rows are returned, the result is `NULL`). Example: `$count = SELECT COUNT(*) FROM T; SELECT * FROM T ORDER BY key LIMIT $count / 2`;

ydb/docs/en/core/yql/reference/yql-core/syntax/_includes/group_by/distinct.md

@@ -4,7 +4,7 @@ Applying [aggregate functions](../../../builtins/aggregation.md) only to distinc
 
 {% note info %}
 
-Applying `DISTINCT` to calculated values is not currently implemented. For this purpose, you can use a [subquery](../../select.md#from) or the expression `GROUP BY ... AS ...`.
+Applying `DISTINCT` to calculated values is not currently implemented. For this purpose, you can use a [subquery](../../select/from.md) or the expression `GROUP BY ... AS ...`.
 
 {% endnote %}
 
@@ -20,5 +20,5 @@ ORDER BY count DESC
 LIMIT 3;
 ```
 
-You can also use `DISTINCT` to fetch distinct rows using [`SELECT DISTINCT`](../../select.md#distinct).
+You can also use `DISTINCT` to fetch distinct rows using [`SELECT DISTINCT`](../../select/distinct.md).