| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
Implemented a column names specification for a WITH CTE. It requires a
column order derivation. It was not working on `YqlSelect` until PR
https://nda.ya.ru/t/qOC3TNqn7gAcy6 was merged. Also there was a bug
with `UNION` column order inference, which is essential for RECURSIVE
queries. There was compatibility problems with `PgSelect` `UNION`
positional column order semantics, so it was tweaked in `YqlSelect`
mode.
commit_hash:c96192270ca6d51eaa0cb39cf59b65c3951ce3fe
|
| |
|
|
| |
commit_hash:c978cba70a9b24aa2e202caa54dc44f419e19468
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes the query <https://nda.ya.ru/t/pYH4zpRH7fw6U4>. If you remove `PRAGMA YqlSelect`,
you'll see that it works on a legacy translation. It is also required to fix PR
<https://nda.ya.ru/t/IZFPoRjS7fw6j8>, because saving a column order makes the bug
visible.
The `nokey` flag of `YqlAgg` callable was renamed to `as_optional` and also an expansion was
fixed by rewriting `MatchType` on `Optional` to `AsOptionalType` to handle `Null` and `pg`
types properly.
commit_hash:dc435437e87006c79bb93984d65931aaf5901af4
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
#### Better error messages for window frame expressions ✎
- Improved error messaging for RANGE window frames to provide more specific information about unsupported column types and invalid ORDER BY expressions
- Removed obsolete error handling for multiple sort columns and simplified the sort traits variant
- Enhanced error reporting with detailed type information when RANGE frames are used with non-numeric or complex expressions
- Added better handling for error types in ORDER BY expressions with improved diagnostic messages including nested error details
- Updated error messages to be more descriptive and actionable, showing the actual column type causing the issue
- Added new test cases covering various error scenarios including NULL types, optional types, and invalid expressions
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:1d2301ac75b3ff7bc9ca97213e9005507654e56b
|
| |
|
|
|
|
|
|
|
|
| |
Implemented a RECURSIVE WITH CTE translation for YqlSelect. It relies on YqlSelf callable.
As this callable binds to enclosing YqlSelect, the diagnostic that subquery can't reference
an enclosing RECURSIVE WITH CTE was added, it is better, that an existing for pgSQL, where
just "table not found" is emitted. The core idea under RECURSIVE handling is that a
"not ready" CTE entry is added to a namespace (with a `nullptr` node), so it can be recognized.
Checked some interesting test cases and wrote TODOs.
commit_hash:65b8646e0615ae070b04822ce7af24245c203bbe
|
| |
|
|
| |
commit_hash:4507aae4a5289d1cf8e95efbac0170ac1b63c956
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first iteration on WITH CTE support. Only simple CTEs are supported.
Properties:
1. Redefinition is forbidden.
2. Shadowing is supported.
3. Nested WITH CTEs are supported.
Following features are not yet implemented:
1. Column names specification. There is an assertion failure at core because
of an absent column order when translating it like for the `PgSelect`.
2. `RECURSIVE` is postponed. There a more sophisticated translation with
`YqlSelf` callable is required.
Also there was a potential defect because of an empty `Id` result not expected.
commit_hash:759676d8a9d369f7eedd9b87f79455b2f8a9fcff
|
| |
|
|
|
|
|
|
|
|
|
| |
#### `YQL-21321`: Adjust type checking for aggregate traits ✎
- Replaced persistable type check with computable type check during aggregate trait validation to allow more flexible type handling
- Added new test cases to verify the behavior of unused aggregate types and ensure proper error reporting
- Updated canonical data and test artifacts to reflect the changes in type checking logic and error messages
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:e14b06e4a135d9aef8ae78a75c3fb23d983365a6
|
| |
|
|
| |
commit_hash:ec28efb62da755bd372bba274c8eaa0f3f5233f3
|
| |
|
|
|
|
|
|
|
|
|
| |
#### Implement MKQL provider for ListJoinCore callable ✎
- Added support for compiling the `ListJoinCore` callable within the MKQL (MapReduce Query Language) provider, enabling its use in query execution plans
- Implemented the necessary type and lambda building logic to correctly handle input structures, key types, and join operations for the new callable
- Updated test configurations to remove xfail status and include new test artifacts for the ListJoinCore functionality, indicating successful integration and testing
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:dbddedaedf354d5e9cf66c69ab3c5f9a3b58cc32
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
#### Implement type annotation for ListJoinCore ✎
- Added type annotation support for the ListJoinCore operator to enable proper type inference and validation during query compilation
- Implemented comprehensive type checking logic that validates input stream structure, key types, and lambda function signatures
- Introduced helper functions to validate argument types and ensure compatibility between input streams and premap lambdas
- Added support for universal type handling to maintain compatibility with existing code patterns
- Included test configuration to verify the implementation and catch potential regressions
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:ea0fd4fbb79c2ccaf60691b6fe648d2657a1fde3
|
| |
|
|
|
|
|
|
|
|
|
|
| |
#### Deep error checking for EnsurePersistable ✎
- Replaced shallow error checking with comprehensive error detection in `EnsurePersistable` functions to ensure all type annotation errors are properly identified
- Introduced new `HasAnyError` function that performs thorough error traversal to catch nested or indirect type errors
- Updated test cases to verify error handling behavior and ensure proper error reporting for incompatible types in SQL operations
- Enhanced type annotation validation to provide more reliable persistence checks for expression nodes
<a href="https://nda.ya.ru/t/qa0kX64r7DqvtN"><font size="2">Autodescription by Yandex Code Assistant</font></a>
commit_hash:019e5924e7d6bdfea7fa46be3da3615b17727b76
|
| |
|
|
| |
commit_hash:867eb4209058a877aa60f86931daddf1e25ac600
|
| |
|
|
| |
commit_hash:10c8d54083c7064e63989ad9c341711fe84409b4
|
| |
|
|
| |
commit_hash:3bc6b3fe94e77b29cd3130cbfba1e1a04df560ee
|
| |
|
|
|
|
|
| |
- Fixed histogram, (bottom/top)(by)?, topfreq, random_(value/sample) over Null
- Disabled DISTINCT with agg phases
- Refactored code by phase predicates extraction
commit_hash:c82f790224e84e542572d5cd270766e3244b4178
|
| |
|
|
| |
commit_hash:1a546dc230518eb6846155c77db762e4d83281d5
|
| |
|
|
| |
commit_hash:7d19863b9dbf9c332d5f8793e47891793fc9091e
|
| |
|
|
| |
commit_hash:feaa364ef3d3f71bfa70a7d64e2cc6e3854d79a5
|
| |
|
|
|
| |
Added switch optimization over extract members
commit_hash:351e8a76ae8ab7fa4e1539588f0253cf8c31eec2
|
| |
|
|
| |
commit_hash:3d559c0475767547557bc9401ecd54bb6c531ee0
|
| |
|
|
| |
commit_hash:eabe9b632535a58658e2ffa4220cd5782df5b2da
|
| |
|
|
| |
commit_hash:048f5c5f1cf2f507a91c2f4cdb24aec0cc71a004
|
| |
|
|
| |
commit_hash:0cd6fc0bf2710bf89ee654ef4c3771c74fb493a6
|
| |
|
|
| |
commit_hash:e420d2d62e3a77af79abbec946f1008c1fa359c6
|
| |
|
|
|
|
|
|
|
|
| |
A feature registry lets us to reference features by name, rather than a concrete langver.
It makes easier to find feature references and releasing incubating features (under max
langver during the development). Features are described at
`yql/essentials/data/language/features.json` and the C++ code is generated. The unit
`feature.h` also introduces a convenience functions to check a feature availability and
emit a standard error message. All features in the translator where replaced with named.
commit_hash:c47f540536212a65f7bc5e8dc6051e73d006be8d
|
| |
|
|
| |
commit_hash:958a606c2956a1155a487070452acc770455bf66
|
| |
|
|
| |
commit_hash:65d1e3053e157375f7a704f1e635467ded5a7ef2
|
| |
|
|
| |
commit_hash:2cb369cb2091489e28790782fe9e7679d367fbb3
|
| |
|
|
| |
commit_hash:5e471728023b5404426daed232c4b00dbba8026c
|
| |
|
|
| |
commit_hash:617264515b5da826be1327cb91b7fc6f6801a835
|
| |
|
|
| |
commit_hash:01842381ef76c8906ec3d33c2dcf2d1ffab107f4
|
| |
|
|
| |
commit_hash:abd1dd6b4cccdb62524bbe3eb1cd2c8b2080c88c
|
| |
|
|
| |
commit_hash:5a7847c000c3e5ec4cadf6880184d3eebb26d3b1
|
| |
|
|
| |
commit_hash:934d9bd00af5903f26796cf610789aaa4a7bf39c
|
| |
|
|
| |
commit_hash:72d0f5c9f96875682a71eb11e67783a723112cce
|
| |
|
|
|
|
|
| |
Canonize more tests
Canonize -F "*window*" -F "*tpcds*" tests
Enable window new pipeline by default
commit_hash:6b5900972f1d065c6956e7ee03e734a80e0c6fa5
|
| |
|
|
| |
commit_hash:23ab69eb08e7c8f74df14dfc43e6109479b8dd15
|
| |
|
|
| |
commit_hash:183e3a952a021c4701c20d6677800f245239d822
|
| |
|
|
| |
commit_hash:13889e43b6156f11945dcee2ab2b59cdb056ce49
|
| |
|
|
| |
commit_hash:cb540d095291ddee3bb60c2d3addee54d23daa1c
|
| |
|
|
| |
commit_hash:a876b0522ba7aa9c9d4af22e749605f0a57343c2
|
| |
|
|
|
|
|
|
|
|
| |
Support `FULL JOIN` and fix `RIGHT JOIN` for `YqlSelect`. The
problem with `RIGHT JOIN` is that in a situation, when we have
`[a, b, c, d, e]` on a stack and are going to "perform" `right`,
all of `[a, b, c, d, e]` are marked optional, because the
`inputIndex` is equal to stack size. But we must mark only
`[a, b, c, d]` as optionals.
commit_hash:b78c5bcecba4b736475d3428918c2a3c377373bb
|
| |
|
|
| |
commit_hash:c998ba15db7c4e5137f44904de85755aa7322e8e
|
| |
|
|
| |
commit_hash:af4c180548bf1699ec6afb335167a4220418386c
|
| |
|
|
| |
commit_hash:054395f57e37951159c1184eae2e6d4bc81245f8
|
| |
|
|
|
|
| |
Now `Grouping` function kindly works, but with some known bug,
that will be fixed in the next PR. It gives 4 TPC-DS queries.
commit_hash:e891401453cbd9d9d964f673053b856e55ea8b56
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for `RowNumber`, `CumeDist`, `NTile`,
`Rank`, `DenseRank`, `PercentRank`, `Lead`, `Lag`, `FirstValue`,
`LastValue` and `NthValue`.
It gives +3 TPC-DS queries and +5 TPC-DS bugs unlocked.
The callable `YqlWin` was introduces, having the following form:
```yqls
(YqlWin
'function_name
'window_name
'() # options
(Void) # type slot
...) # args
```
During the callable type annotation and expansion the same code
for implementation functions substitution is used and shared even
with a pgSQL.
There was an issue with a `listType` for `YqlAgg`, `YqlAggWin`
and `YqlWin`, because it was built incorrectly by referencing
an atom "row" instead of _that_ argument row. It is fixed with
a new "type slot". Now it has 3 states: `(Void)`, which is set
by translator just as a stub, `row` that is set by
`YqlSetItemWrapper` during the `RebuildLambdaColumns`, so then
on the `YqlWin` type annotation it can take this `row` and wrap
it to the `listType`, pass to the function and call for a
repetition, so in a next stage the `resultType` will be ready.
commit_hash:256fc2cb359714a646a308359b340b1715919f5d
|
| |
|
|
| |
commit_hash:a201cbc3a08b7bad471d4d6a15f3dfc3f63d989b
|
| |
|
|
| |
commit_hash:be492d367e30019197d70cb6484fd3b1ce6a9481
|