| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Изменения в рамках этого тикета <https://github.com/ydb-platform/ydb/issues/44190>
#### Support Uuid and DyNumber in minikql blocks and Arrow ✎
- Added support for Uuid and DyNumber data types within MiniKQL blocks and Arrow computations, enabling their use in block-based operations and serialization
- Implemented proper conversion, serialization, and deserialization logic for both data types in the Arrow format
- Extended block item handling to support Uuid and DyNumber, including comparator and hasher implementations
- Added comprehensive unit tests covering roundtrip operations, serialization, comparison, and conversion for both data types
- Integrated Uuid and DyNumber support into built-in functions like Min/Max and their aggregate variants
- Updated type system and block builder components to recognize and handle the new data types correctly
- Added necessary includes and utility functions to work with Uuid and DyNumber in MiniKQL contexts
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:d1ab82c060cfa90b7cd13a1cb3efbcb9615e6291
|
| | | |
| | |
| | |
| | | |
commit_hash:f831c95aaaa6c6f2c4b98c74539633213dd00bd3
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
#### 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
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:0dec4e34cf45e66962a8e8884c6cee893ad3dfb2
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \ |
|
| | |/ / |
|
| |/ / |
|
| |\ \ |
|
| | | | |
|
| | |\| |
|
| | | |
| | |
| | |
| | |
| | | |
Migrate to incrementalAllowDenyList and sync .a cryptoghraphy
commit_hash:93cb82180199c2a68dd8ca93cb7ebca7a500accf
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Cherry-picked original "Fix YQL native YT type flags" and "Fix YT native types handling for aux columns - 2" with additional fixes (previously reverted)
- Enforce mandatory usage of the type v3 schema for output tables
- Major refactoring of Skiff encoder/decoder to fix non-complex nativeness support
commit_hash:2b4241624a261a690c916a7386b84cb3d483a373
|
| | | |
| | |
| | |
| | | |
commit_hash:bc73ed520d5d4ef210b03b983720e6e8a6996db5
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
#### Enable misc-unused-using-decls check ✎
- Enabled the `misc-unused-using-decls` clang-tidy check to enforce removal of unused using-declarations
- Removed several unused using-declarations across multiple files to comply with the new check
- Updated clang-tidy configuration to activate the check instead of suppressing it
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:5dd7bcf766b71f2041902fbf314e13f2b81d9a4d
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
#### Support TCoreAttr::Args at SqlCore ✎
- Introduces support for extended SQL flags with arguments in the SqlCore configuration, allowing flags to carry additional parameters for more granular control
- Refactors internal flag handling to use a map-based structure instead of a simple set, enabling storage and processing of flag arguments
- Updates module resolver and translation settings parsing to work with the new extended flag format, ensuring proper flag propagation and application
- Adds new infrastructure for parsing and managing SQL translation flags with arguments, including dedicated parsing logic for specific flag types
- Maintains backward compatibility while enabling new functionality for SQL flag configuration through gateways and command-line options
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:8b26974b3bf4ff2bdaf76715cbb210a8a15e1dad
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
#### Support PruneUnusedColumns in Materialize ✎
- Adds support for the `prune_unused_columns` setting in Materialize operations, enabling optimization to remove unused columns from materialized tables
- Extends the YtProvider to recognize and validate the new PruneUnusedColumns setting for both Materialize and Persist operations
- Implements optimizations to handle column pruning in Materialize operations, including handling ExtractMembers over Materialize cases and multi-usage scenarios
- Updates physical finalizing logic to properly handle Persist operations with PruneUnusedColumns setting
- Adds new test cases to verify the functionality of column pruning in Materialize operations with various filtering scenarios
- Modifies existing tests to reflect changes in behavior and ensure compatibility with the new optimization feature
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:83c18981b8767ac2b789c1b1ae81aaa1ee164a92
|
| | | |
| | |
| | |
| | | |
commit_hash:df49de36e4fa0429d86b2e4a6e93b71c8fa4120f
|
| | | |
| | |
| | |
| | | |
commit_hash:6d43e40e3fc61909be6097a1ac9b29e463377aef
|
| | | |
| | |
| | |
| | | |
commit_hash:d8b7c078f33c790505bdf3cdc0a7c3f015afb0cd
|
| | | |
| | |
| | |
| | | |
commit_hash:6d7e16c90579ca09663448dc34d8d289191d444f
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
#### Fix use-after-poison issue in MKQL arrow allocator ✎
- Addressed a use-after-poison memory error that occurred when using the default arrow allocator for memory management in MKQL
- Added a sanitizer call to make memory region accessible before freeing it, preventing undefined behavior in memory sanitization tools
- Introduced a new unit test to verify proper allocation and deallocation when the default arrow allocator is active
- Ensured memory safety by properly handling memory access patterns during deallocation in sanitizer environments
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:080ee439f355ca7178f78b02b52302928e60e745
|
| | | |
| | |
| | |
| | | |
commit_hash:5c782ac7ebeef7ea9942ba51758be63848e54d98
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | | |
Co-authored-by: Alexander Zalyalov <[email protected]>
|
| | | |
| | |
| | | |
Co-authored-by: Raubzeug <[email protected]>
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
New schemeshard admin action `MoveToStoragePool` moves a shard to another storage pool.
- Button on the shard-info page
- Target storage pool is picked from the database's storage pools
- Moving a shard is really a rebinding of all the tablet's channels to the target storage pool
- Done by sending `CreateTablet` with the updated channel bindings to the Hive
- New bindings are persisted on the Hive's ack (`CreateTabletResult`)
- Failure to get an ack leaves nothing persisted on the schemeshard side
- So the action can be retried
- `CreateTablet` is idempotent — sending it more than once does no harm
- Still, moving a shard to the storage pool it's already on is a no-op
- Unless the confirmation box (next to the button) is checked to force the send to the Hive
The action is universal — works for any subdomain's shard/tablet.
On a tenant schemeshard, a shard-info page can show empty channel bindings: those shards are the tenant's system tablets (their channel bindings live only on the root schemeshard). In that case there's no button (the move is rejected); the UI links to the root schemeshard page instead, with an explanation.
|
| | | | |
|
| | | |
| | |
| | | |
Co-authored-by: Alexander Kotov <[email protected]>
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | | |
Co-authored-by: Artem Ermoshkin <[email protected]>
|
| |\ \ \
| |/ /
|/| | |
|
| | | | |
|
| |/ / |
|
| | | |
|
| | | |
|
| | |
| |
| | |
Co-authored-by: Kirill Vasilenko <[email protected]>
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|