ydb/yql/essentials/sql/v1, branch main

Intermediate changes

2026-07-23T16:44:21Z

commit_hash:e9f9f235622634ecdf8656af507d5c1ba8dc0375

Add CREATE IF NOT EXISTS, CREATE OR REPLACE, ALTER/DROP IF EXISTS for SECRET operations

2026-07-23T13:17:44Z

#### Add CREATE IF NOT EXISTS, CREATE OR REPLACE, ALTER/DROP IF EXISTS for SECRET operations ✎ - Introduce support for `CREATE IF NOT EXISTS` and `CREATE OR REPLACE` syntax for secret creation, allowing conditional secret creation based on existence - Add `ALTER IF EXISTS` and `DROP IF EXISTS` syntax for secret modification and deletion, preventing errors when operating on non-existent secrets - Extend secret operation parsing to handle optional keywords for conditional operations while maintaining backward compatibility - Update secret parameter validation and error handling to support new conditional operation modes - Add comprehensive test coverage for all new conditional secret operations including error cases and expression support Autodescription by Yandex Code Assistant commit_hash:5da22cd6acc7bb610627c562280556c497d57a10

YQL-21333: Refactor sql/v1/translation

2026-07-23T06:46:01Z

commit_hash:9ad4de6a95ef5173379f58dc372a6b208386f34b

YQL-21350: Limit SQLv1 parse tree depth

2026-07-21T18:39:47Z

Copy of https://nda.ya.ru/t/ceJZ5osd7jHYXe. commit_hash:07f1b0533bb4ba214af84233eee20c113010fa09

YQL-20631: Warn on WITH CTE name mismatch

2026-07-21T15:12:31Z

A warning on WITH CTE column names specification and corresponding select column order mismatch was introduced. It is not complete, because there can be autogenerated columns (e.g. `column0`, `column1`) and now there is no way to get if they are autogenerated or user-specified, so there is a regex heuristic now. Good implementation requires passing a new attribute from a translator and a lot of recanonization. I can do it, but propose to make it in a separate PR. Also there was a problem of repetitive warning emission, because of "Type Annotation (repeat)". A classical approach with `Warn` suffix is not very useful in SqlSelect, because its type annotation is so huge and has a lot of `Repeat`s. So I found a solution in introduction of a new attribute `warnings`, where warning ids are stored in an atom list, so lookup in this list does the deduplication. commit_hash:e67198223e224ef80ff2bf48d6d9bb7bbe3f264a

Add GENERATED ALWAYS AS syntax

2026-07-17T10:08:59Z

#### Add GENERATED ALWAYS AS syntax support ✎ - Introduces support for GENERATED ALWAYS AS column syntax in CREATE TABLE and ALTER TABLE statements, including both STORED and VIRTUAL variants - Adds parsing and semantic validation for generated columns, ensuring they are only supported for YDB provider and table types - Extends SQL grammar with new keywords and rules to handle generated column definitions and expressions - Implements proper highlighting and formatting for GENERATED ALWAYS AS syntax across different language parsers - Includes comprehensive test coverage for various generated column scenarios, including expressions, nested paths, and error conditions - Adds validation to prevent usage in external tables, tablestores, and non-YDB providers Autodescription by Yandex Code Assistant commit_hash:cb2260d56b17f0d8e9044dcebc59a25147e85bd6

YQL-21408: Replace MakeLangVersion with features.json

2026-07-15T12:13:42Z

#### Replace MakeLangVersion with features.json-based feature system ✎ - Introduces a new feature system based on `features.json` to manage language version dependencies instead of hardcoded `MakeLangVersion` calls - Replaces direct language version checks with references to named features defined in JSON configuration - Adds validation and initialization logic for features to ensure version consistency - Updates all existing language version checks to use the new feature-based approach - Centralizes feature version definitions in a single JSON file for better maintainability and clarity Autodescription by Yandex Code Assistant commit_hash:fe9823c0442060337a30186fd957ae294f1aa1c2

YQL-21404 implemented syscache, table, func call

2026-07-14T14:57:28Z

#### `YQL-21404`: Implemented syscache, table, and function call support for collations ✎ - Added support for PostgreSQL collation handling in function calls, enabling explicit collation specification via named arguments - Implemented syscache and table catalog support for pg_collation system table to provide complete catalog information - Enhanced type annotation and runtime compilation to properly handle collation OIDs and validate collation names - Introduced ICU locale collation support with stable OID assignment based on locale position in generated catalog - Added comprehensive test coverage for collation functionality including standard and ICU locales, collation validation, and error cases - Extended SQL parsing to support COLLATE clauses and proper collation propagation in function calls Autodescription by Yandex Code Assistant commit_hash:e9a32cc848bef7b68b4f57f71a1f5f69e0de9653

Watermarks: YQL: allow watermark options

2026-07-14T13:02:19Z

#### Allow watermark options in YQL ✎ - Extend watermark functionality to support additional configuration options such as watermark granularity and idle timeout - Modify internal representation to include watermark settings as a separate parameter in watermark generator nodes - Update SQL parser to recognize and process watermark-related hints with proper validation - Add validation logic to ensure watermark options conform to expected format and types - Introduce unit tests to verify the new watermark option parsing and handling Autodescription by Yandex Code Assistant commit_hash:76e9ae7e1709a2bcd8cd2ccaaf132ceedac0517f

Change `MATERIALIZE` grammar to exclude `WITH` statement ambiguity

2026-07-10T15:57:46Z

#### Change MATERIALIZE grammar to exclude hints ambiguity ✎ - Restructured the MATERIALIZE statement grammar to resolve ambiguity between table hints and cluster specification by reordering clauses to place hints after the target cluster - Updated minimum language version requirement for the MATERIALIZE feature to 2026.02 - Modified format tests and validation logic to align with the new grammar structure - Added tests for single and multiple hints to ensure proper parsing and handling - Updated canonical test outputs to reflect the new syntax order with hints positioned after the INTO clause and before the ON clause Autodescription by Yandex Code Assistant commit_hash:0dec4e34cf45e66962a8e8884c6cee893ad3dfb2