<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ydb/yql/essentials/sql/v1/node.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>YQL-20247 Depends for Udf function</title>
<updated>2025-08-05T17:39:19Z</updated>
<author>
<name>vvvv</name>
<email>vvvv@yandex-team.com</email>
</author>
<published>2025-08-05T17:15:00Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=4d576a194855d3d3725914b7330af3f6478e0e13'/>
<id>urn:sha1:4d576a194855d3d3725914b7330af3f6478e0e13</id>
<content type='text'>
commit_hash:4ee9d9b9079b90e8eeb91accc41d6a3a30c3a18c
</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-20086 sql</title>
<updated>2025-06-18T12:49:04Z</updated>
<author>
<name>vvvv</name>
<email>vvvv@yandex-team.com</email>
</author>
<published>2025-06-18T12:12:37Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=379a419911ee1bbb93f56085133712fa5d8c3112'/>
<id>urn:sha1:379a419911ee1bbb93f56085133712fa5d8c3112</id>
<content type='text'>
commit_hash:b06f3d2f5fa81e2073966eb172758758bd94fdf2
</content>
</entry>
<entry>
<title>support database settings in ALTER DATABASE</title>
<updated>2025-06-04T09:51:33Z</updated>
<author>
<name>deminds</name>
<email>deminds@yandex-team.com</email>
</author>
<published>2025-06-04T09:36:47Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=14c42c6f9a85a081cde9ba58db0b008b3ade11f7'/>
<id>urn:sha1:14c42c6f9a85a081cde9ba58db0b008b3ade11f7</id>
<content type='text'>
The main goal is to enable setting SchemeLimits (ShardsLimit and PathsLimit) via YQL.

Issue:
- https://github.com/ydb-platform/ydb/issues/16742
commit_hash:e873849e3b4bb494e349ccebbb1ff6d51655c5d1
</content>
</entry>
<entry>
<title>New CHANGEFEED's option: SCHEMA_CHANGES</title>
<updated>2025-06-03T09:51:48Z</updated>
<author>
<name>ilnaz</name>
<email>ilnaz@yandex-team.com</email>
</author>
<published>2025-06-03T09:11:48Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=3e8add594e2ff4cf7ff8f552e9a6e285f4d6c372'/>
<id>urn:sha1:3e8add594e2ff4cf7ff8f552e9a6e285f4d6c372</id>
<content type='text'>
commit_hash:23ba332ac8979f2e4e62231fb47414233ee4043e
</content>
</entry>
<entry>
<title>YQL-19747 sql functions</title>
<updated>2025-03-28T18:52:08Z</updated>
<author>
<name>vvvv</name>
<email>vvvv@yandex-team.com</email>
</author>
<published>2025-03-28T18:08:12Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=76a438f2d7f4c7cb366eff6974bb20378568a2c2'/>
<id>urn:sha1:76a438f2d7f4c7cb366eff6974bb20378568a2c2</id>
<content type='text'>
commit_hash:9f628fe1894ee7dcdcbdd161855b668ca6e7380f
</content>
</entry>
<entry>
<title>Fix bug in ALTER USER with set null password</title>
<updated>2025-03-06T14:51:31Z</updated>
<author>
<name>flown4qqqq</name>
<email>flown4qqqq@yandex-team.com</email>
</author>
<published>2025-03-06T14:32:09Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=82a5981c8a3a21d7cc17551fac0c1513f3cbf95a'/>
<id>urn:sha1:82a5981c8a3a21d7cc17551fac0c1513f3cbf95a</id>
<content type='text'>
До этого, при любом запросе ALTER USER без опции PASSWORD выставлялось значение Null Password как дефолтовое - это баг, потому что при модификации пользователя не надо выставлять вообще никакого значения.
commit_hash:3cb3d5bb3e9487439787deb9102cd0105b6b9e82
</content>
</entry>
</feed>
