<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ydb/yql/essentials/sql/v1/sql_ut_common.h, branch oidc-1.2.6.0-dev</title>
<subtitle>Mirror of YDB github repos</subtitle>
<id>https://code.mastervirt.ru/ydb/atom?h=oidc-1.2.6.0-dev</id>
<link rel='self' href='https://code.mastervirt.ru/ydb/atom?h=oidc-1.2.6.0-dev'/>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/'/>
<updated>2025-08-22T14:36:11Z</updated>
<entry>
<title>Add external_data_channels_count create table feature (SQL part)</title>
<updated>2025-08-22T14:36:11Z</updated>
<author>
<name>Anton Romanov</name>
<email>a-romanov@nebius.com</email>
</author>
<published>2025-08-22T14:14:11Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=a2caee2426b884f5f71512d59f69a284759397cd'/>
<id>urn:sha1:a2caee2426b884f5f71512d59f69a284759397cd</id>
<content type='text'>
Can I use your `soroka` for push YQL part of a new feature for YDB, please?

[There](https://github.com/ydb-platform/ydb/pull/21672) is the original PR approved  by Fomichev an Puchin which can't be committed directly to YDB github.

Type: feature
Component: yql

---
Co-authored-by: Tony-Romanov [150126326+Tony-Romanov@users.noreply.github.com]

Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1414
commit_hash:c98a7b656a050b09976f22f1470ba0ab5bbb52c2
</content>
</entry>
<entry>
<title>Add new option CACHE_MODE in FAMILY settings</title>
<updated>2025-08-22T13:19:41Z</updated>
<author>
<name>ivannik</name>
<email>ivannik@yandex-team.com</email>
</author>
<published>2025-08-22T12:56:27Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=5c41dc204afed4149a10517c7f1ac7a234ceed8c'/>
<id>urn:sha1:5c41dc204afed4149a10517c7f1ac7a234ceed8c</id>
<content type='text'>
RFC: https://nda.ya.ru/t/vPsncOoC7HttdF
GitHub Issue: https://github.com/ydb-platform/ydb/issues/18695
commit_hash:96445a9aef7b1fede372b9e4c60b30eb9ef5fdc1
</content>
</entry>
<entry>
<title>Watermarks: add time extractor to HoppingWindow</title>
<updated>2025-08-14T10:10:46Z</updated>
<author>
<name>vokayndzop</name>
<email>vokayndzop@yandex-team.com</email>
</author>
<published>2025-08-14T09:16:50Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=618abcfd3763bc44abbc9ef934a8b1d71dc9c674'/>
<id>urn:sha1:618abcfd3763bc44abbc9ef934a8b1d71dc9c674</id>
<content type='text'>
commit_hash:d54496a7e3d9bd72e53ce880691a59490a34a138
</content>
</entry>
<entry>
<title>YQL-20257: Parse cluster at simple_table_ref bind_parameter</title>
<updated>2025-08-13T14:02:13Z</updated>
<author>
<name>vitya-smirnov</name>
<email>vitya-smirnov@yandex-team.com</email>
</author>
<published>2025-08-13T13:27:43Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=3b79116cac370b648c75323b866927d32aab08f4'/>
<id>urn:sha1:3b79116cac370b648c75323b866927d32aab08f4</id>
<content type='text'>
- Add `cluster_expr` to `simple_table_ref_core` alternative.
- Added `Sql2Yql` unit test with a statement that is
  not parsed on trunk: https://nda.ya.ru/t/qHRri7r57HK3r2.
commit_hash:eada89e88e3f2bc03c47cd22b73ba58b75f20681
</content>
</entry>
<entry>
<title>YQL-20280: Warn on ASSUME ORDER BY usage after UNION</title>
<updated>2025-08-11T14:20:05Z</updated>
<author>
<name>vitya-smirnov</name>
<email>vitya-smirnov@yandex-team.com</email>
</author>
<published>2025-08-11T14:06:05Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=4c07961e6209762036c1cade4af1309db4b33225'/>
<id>urn:sha1:4c07961e6209762036c1cade4af1309db4b33225</id>
<content type='text'>
commit_hash:a9c400c784ed04924390abb11509664e6576a3b7
</content>
</entry>
<entry>
<title>Watermarks: DDL</title>
<updated>2025-08-08T13:39:46Z</updated>
<author>
<name>vokayndzop</name>
<email>vokayndzop@yandex-team.com</email>
</author>
<published>2025-08-08T13:11:35Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=2c274bc53d8b06b40ef04a656f5665e0ba94a63d'/>
<id>urn:sha1:2c274bc53d8b06b40ef04a656f5665e0ba94a63d</id>
<content type='text'>
commit_hash:64ad6b4138ee27f474b440e8ef3e07fac1935346
</content>
</entry>
<entry>
<title>New ASYNC REPLICATION's option: CA_CERT</title>
<updated>2025-07-21T14:07:14Z</updated>
<author>
<name>ilnaz</name>
<email>ilnaz@yandex-team.com</email>
</author>
<published>2025-07-21T13:10:13Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=bd13b1b03f862c3fb50c30c35cd976376c9d63ae'/>
<id>urn:sha1:bd13b1b03f862c3fb50c30c35cd976376c9d63ae</id>
<content type='text'>
commit_hash:ce61d0c6dad2e170eface04d63918adc1082e56e
</content>
</entry>
<entry>
<title>Feature: alter table T alter column C set not null</title>
<updated>2025-07-21T12:11:34Z</updated>
<author>
<name>flown4qqqq</name>
<email>flown4qqqq@yandex-team.com</email>
</author>
<published>2025-07-21T11:57:17Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=646c5b82467945d8cdfc5d5f716ae2acb30a8313'/>
<id>urn:sha1:646c5b82467945d8cdfc5d5f716ae2acb30a8313</id>
<content type='text'>
Когда-то давно (когда еще YQL жил в github) была поставлена задача - поддержать SET/DROP NOT NULL на колонку. DROP NOT NULL был сделан и давно уже существует в main: &lt;https://github.com/ydb-platform/ydb/pull/6342&gt;.

Однако с SET NOT NULL возникли определенные сложности, поэтому был сделан отдельный пулл реквест: &lt;https://github.com/ydb-platform/ydb/pull/6341&gt;. Как видно, ПР так и не вмержили по причине увольнения автора кода. Недавно задача всплыла вновь, поэтому надо доделать.

В этом пулл реквесте добавляется код в грамматику YQL новое выражение - `ALTER TABLE t ALTER COLUMN c SET NOT NULL`, которая добавляет ограничение `NOT NULL` на колонку.
commit_hash:f310061b13666418c46309ea32032fbce68fb865
</content>
</entry>
<entry>
<title>YQL-20171: Fix aggregation joining key</title>
<updated>2025-07-15T14:19:51Z</updated>
<author>
<name>vitya-smirnov</name>
<email>vitya-smirnov@yandex-team.com</email>
</author>
<published>2025-07-15T14:01:51Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=64137fb0cbe9afe92dca8efc335ef9ff16b78926'/>
<id>urn:sha1:64137fb0cbe9afe92dca8efc335ef9ff16b78926</id>
<content type='text'>
There was a bug with a aggregation deduplication
by a column at the translator.

For a single column the system joining all
aggregations using the generic key. The
generic key was just a column name without
source name what leads to collision when
aggregating multiple different sources with
same column names.

This patch fixes the generic key by adding a
data source name there. Also tests are added.
commit_hash:1c0a9da512f68c58d2830e096de76b769b733cb2
</content>
</entry>
<entry>
<title>YQL-17269: Support UNION/INTERSECT/EXCEPT combinations</title>
<updated>2025-07-09T11:38:43Z</updated>
<author>
<name>vitya-smirnov</name>
<email>vitya-smirnov@yandex-team.com</email>
</author>
<published>2025-07-09T11:16:01Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=59c3167c208900bb714ff5cc477476e3ab14f4f0'/>
<id>urn:sha1:59c3167c208900bb714ff5cc477476e3ab14f4f0</id>
<content type='text'>
Introduce `UNION` and `INTERSECT/EXCEPT` grammar rules
for precedence. Rewrote `Build` procedure into `BuildStmt`,
`BuildUnion`, `BuildIntersection`. Added tests, modify format.

It took a lot of time trying to adapt the existing `Build` procedure.
The I noticed that the logic for `union` and `intersection` is
different, since `union` groups arguments into bundles, but
`intersection` is a strictly binary operation.
commit_hash:70008ae3c2603364b6dfbeeb189fdc7f5237433d
</content>
</entry>
</feed>
