| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
commit_hash:632e24794e8bcf6ef0502b7e8c031e964d28d36a
|
| |
|
|
| |
commit_hash:67576d4a9e4a1f4bbbb204bcb0b98c255009b1da
|
| |
|
|
|
|
| |
Now it is possible to pass clusters schema
via a JSON file using `-s` flag.
commit_hash:fd579430968881627c77d4586464952176134dc5
|
| |
|
|
|
|
|
|
| |
When table `folder/table` exists. On prefix
``` SELECT * FROM `folder/ ``` users want to
accept ``` table` ``` rather than just `table`.
This patch is about it.
commit_hash:12d36cbf037db91f49136ab8e013b160a28b5b1b
|
| |
|
|
| |
commit_hash:56c7deefce71a95f10a4738b0a51e6ba384dd983
|
| |
|
|
| |
commit_hash:6d67ec1fa5023083debd89aaa99950019ca37c90
|
| |
|
|
| |
commit_hash:b06f3d2f5fa81e2073966eb172758758bd94fdf2
|
| |
|
|
|
| |
Added support for token filtration. It is needed because YQL grammar supports multiple systems with various capabilities. For example, some of those do not support `INTERSECT ALL` and therefore `ALL` after `INTERSECT` should be *disabled*. Another example is a support of an only `EVALUATE FOR`, so `FOR` is *forced* to be precendenced by `EVALUATE`.
commit_hash:a926c8d3911f8dd025ab58eb7f81e2370fcd9376
|
| |
|
|
|
| |
Added support for a columns completion at a simple select. For example, `` SELECT # FROM hahn.`home/yql/tutorial/users` `` и `` USE hahn; SELECT $ FROM `home/yql/tutorial/users` ``.
commit_hash:2254449e91255c19792a1dc521825e44dda7d63b
|
| |
|
|
|
| |
Instead of relying on keyword sequences provided by C3 and using hacks like pattern matching on keyword sequences (`format.cpp`), emit composite types manually.
commit_hash:999d8d4b514433fbdf7885aa0122b2010e985efb
|
| |
|
|
| |
commit_hash:6e56cbea6a1c12b4f9e6b065eedf177763a329d2
|
| |
|
|
| |
commit_hash:6db0e8f89d5131fe035c10bdaa61312e2a3a72db
|
| |
|
|
| |
commit_hash:c8d74820e197343a1019edeff4f8c21fc5805244
|
| |
|
|
|
|
|
|
|
|
|
|
| |
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/62
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1323
commit_hash:ebab6c3290ba984174c85bba35eeb066b53af5aa
|
| |
|
|
| |
commit_hash:4ad0e146a3e92836d6aec7eaac00ae0225484b09
|
| |
|
|
| |
commit_hash:a5cf347a0fdbf87672444c86b9acad24d4ab956a
|
| |
|
|
|
|
|
|
|
|
|
| |
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/52
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1321
commit_hash:ef8af2fa618e6fc316d7a6cf348b7f737bb0cfb4
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clang Tidy is cool, but too slow ;(. Btw, should we respect `misc-include-cleaner` check?
```bash
ya dump compile-commands > /tmp/cc/compile_commands.json
find . -type f \( -name "*.cpp" -o -name "*.h" \) -exec clang-tidy {} -p /tmp/cc {} -checks="misc-*" \;
```
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1305
commit_hash:c2ecf638062dcdd0730fed3381da4a230f5352c3
|
| |
|
|
| |
commit_hash:98cd4d4370d009f6e71e69219f5b9d89ab3eca9e
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
commit_hash:23ba332ac8979f2e4e62231fb47414233ee4043e
|
| |
|
|
| |
commit_hash:6476b453be16b7db003e75789e3b630c1168f14f
|
| |
|
|
|
|
|
|
|
|
|
| |
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/39
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1307
commit_hash:782732c290cf2894ec466d2fbb5d0e96905f1804
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Introduced scoped name collection at global analysis
- Added `BingingsNameService` constructed after global analysis and united with the base service.
- Added dollar detection at local analysis.
After this point design should be reexamined and module should be refactored.
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/57
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1304
commit_hash:a7bf41703f0ee846e359407b53a5d62fc05928ea
|
| |
|
|
| |
commit_hash:ab24b3db82789b77ad465efa64de93c5eab43629
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Completion candidates comes unclosed from right and with zeroed `CursorShift`. In future there will be an atomic patch that will close candidates and set `CursorShift` correctly. Not it is zeroed to integrate with clients (e.g. YDB CLI).
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/53
- Related to https://github.com/ydb-platform/ydb/issues/9056
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1299
Co-authored-by: vvvv <[email protected]>
commit_hash:38bcd21f0d6959275af89a981fd9b296374aea51
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a mistake thinking that provider is a part of a cluster name. Actually `yt:saurus` and `saurus` are same clusters and provider (`yt`) serves only as a hint for translation expressions such as `yt:$cluster_name`.
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/54
- Related to https://github.com/ydb-platform/ydb/issues/9056
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1301
commit_hash:19a45cf0bb6c7dda26747b2e3371646272f79bce
|
| |
|
|
| |
commit_hash:d002e9690bd7cbd1874fdbfe454c9f7a00256839
|
| |
|
|
|
|
|
|
|
|
|
| |
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/50
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1292
commit_hash:a6d543bc18b2f9239bf0b33afd8497a7919fe4b3
|
| |
|
|
| |
commit_hash:03cd7489d5021112dd8bb61893361b17637d37d1
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> no such statement
> sql_stmt: (EXPLAIN (QUERY PLAN)?)? sql_stmt_core;
> I suggest to add it always if needed for c3
---
- Related to `YQL-19747`
- Related to https://github.com/ytsaurus/ytsaurus/pull/1289
- Related to https://github.com/vityaman/ydb/issues/39
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1297
commit_hash:7b1a8947fdd5d8c6b737e781f2288632359f569d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I leaved the YDB configuration empty as need your feedback.
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/39
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1289
commit_hash:408c7e0f101027fc6ca3d86d251b5639fcae07bb
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Changelog entry
Type: fix
Component: yql
Fix parsing unique index type. There was an error that, if not specified explicitly (SYNC or ASYNC), index type remained with the default value GLOBAL SYNC, despite that it was explicitly specified as UNIQUE in query.
https://github.com/ydb-platform/ydb/issues/17885
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1287
commit_hash:60de1b723fb1229f2197087fe21db67c72ccbd13
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The simplest solution actually is an SQL injection.
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/ydb-platform/ydb/pull/18146
- Related to https://github.com/vityaman/ydb/issues/46
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1283
commit_hash:7043e7cdd1e0d378926783d31cf5f8e055393aaa
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce global analysis which will be extended with more ParseTree analysis later.
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/40
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1281
commit_hash:848fb3fdd6bc9612769c47d66198fca018ff465f
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On `SELECT * FROM pn` it completed to `SELECT * FROM ppnv1`, but expected ``` SELECT * FROM `pnv1` ```.
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/44
- Related to https://github.com/ydb-platform/ydb/pull/18146
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1280
commit_hash:e937239fae7bf609bde6358b9b27c2b504c8ba32
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix `TRegexLexer` performance. Now it is just 2 times slower than a reference ANTLR implementation on Release mode, so merged regexes are 3 times better than scan&compare.

---
- Related to `YQL-19616`
- Related to https://github.com/ydb-platform/ydb/issues/15129
- Related to https://github.com/vityaman/ydb/issues/42
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1278
commit_hash:1529f641172fea13f0d33fbfd06a4827c6efde01
|
| |
|
|
| |
commit_hash:6b048925e9cf8eede1e184503d43f211b3be6dbd
|
| |
|
|
| |
commit_hash:2e70854d1aaae271baa81e098f791d9f4d54ddeb
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes superfluous candidates (`OPTIONAL`, `CALLABLE`, ...) at `SELECT * FROM #`.
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1273
commit_hash:d34d81ea86b8b6b5d339174be20d14d0371c3de6
|
| |
|
|
| |
commit_hash:d39880b60ceb7a5978a9ed1b8b95cfaf3c184373
|
| |
|
|
| |
commit_hash:9780948e26ef2e689d26520b76fefa0794efdd9e
|
| |
|
|
|
|
|
|
|
|
|
|
| |
---
- Related to `YQL-19747`
- Related to https://github.com/vityaman/ydb/issues/8
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1268
commit_hash:76e4e2c8b225994cc842c1ee00a0ec8e6eed5c05
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Outcomes:
1. Need to think more deeply about library interfaces. If you think that an interface is redundant, think again, because author knows a usecase that you do not imagine.
2. If you are lazy now to implement something robustly, think twice because the day will come and this code
will fire.
The problem was that on input ``` ... cluster.`/yql/t#` ``` C3 receives only a prefix ``` ... cluster.`/yql/t ``` and a token stream produced was incorrect and therefore completions too.
---
- Related to `YQL-19747`
- Related to https://github.com/ytsaurus/ytsaurus/pull/1257
- Related to https://github.com/ydb-platform/ydb/issues/9056
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1271
commit_hash:8bf5f2683c9e41963003da923f255f63b898aac5
|
| |
|
|
| |
commit_hash:5fe1ef25f8ddc098a82ee48c8f39ac413905f659
|
| |
|
|
| |
commit_hash:3a624a323006078de71f50747f7b2e8cadba7ccd
|
| |
|
|
| |
commit_hash:13ef56a642595d0dc7336b790971a5ed9155163f
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
---
- Related to `YQL-19747`
- On top of https://github.com/ytsaurus/ytsaurus/pull/1253
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/14
- Related to https://github.com/vityaman/ydb/issues/35
- Related to https://github.com/vityaman/ydb/issues/40
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1257
commit_hash:0b842abb27184c88b8177beeea29fb1ea86b7a04
|
| |
|
|
| |
commit_hash:9d5644514d892de24a7e9625590c95a4549b0a46
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We faced with a failing assertion at `NYql::NormalizeName`. This patch expects it and fallbacks to `ToLowerUTF8`.
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/38
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1255
commit_hash:946162904ce3b74f490debb7f9e0587f136b4075
|