| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
- Added table functions completion.
- Also fixed a bug when USEd cluster
was not added to table context at table
function argument.
- Complete folder names at `prefix`
of `LIKE`, `RANGE`, etc.
commit_hash:26be383be728796e8431f906e2815acd77645ad4
|
|
|
|
|
|
| |
I missed that a query parameter key starts with
'$'.
commit_hash:1a24953b4f837da31db2201b9a9ffd0eef0c6b34
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
commit_hash:a497dfe8863a864913c1d6df4b28edbe7d8e4bba
|
|
|
|
|
|
| |
Related to <https://nda.ya.ru/t/DMAUQona7GBKMA>.
There was a problem with a binding ranking.
commit_hash:6dbd96ec883562c4e03778a8487b2843be189ce7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LSP supports the following propoerty of the
completion item, that supports Markdown format:
```
/**
* A human-readable string that represents a doc-comment.
*/
documentation?: string | MarkupContent;
```
I added docs only for a few items just to check a
look in the UI. Also some docs are shortened.
Documentation is opt-in decorator for a
NameService. Because it is not needed in the
YDB CLI, for example.
commit_hash:b400ed1224be2906b7fb1da29e9c97aa7578d710
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- YQL-19747: Remove unused header
- YQL-19747: Remove NameSet alias
- YQL-19747: Fix identifier typo
- YQL-19747: Cosmetics
- YQL-19747: Receive NameRequest as const ref
- YQL-19747: Remove string_util.h
- YQL-19747: Change engine.Complete
- YQL-19747: Remove configuration typedef
- YQL-19747: Rename context to local
commit_hash:451a6ba7c08e670a492222a29463be40a627c867
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LSP protocol has a property
```
/**
* A string that should be used when filtering a set of
* completion items. When omitted the label is used as the
* filter text for this item.
*/
filterText?: string;
```
It is useful, e.g. when we prepend some punctuation
at a candidate content, but still want to filter by
prefix, ignoring that punctuation.
Related to https://nda.ya.ru/t/KCkzjhXS7G3Epg.
commit_hash:01f258218d312eef764350bd4d78da15acb8c9ea
|
|
|
|
| |
commit_hash:79ad481a8734a11e954d4a38e1218b17e116700c
|
|
|
|
|
|
|
|
|
| |
Also fixed a bug when the same table used with
and without an alias produced duplicated column
names. This is incorrect at translator, but anyway
we need to handle it gracefully. Also refactored
some utility methods like context union.
commit_hash:45a12675e865bb9d929e5e5178e16239a763d1f5
|
|
|
|
|
|
| |
Table can have not `ID_PLAIN` columns and we
should return them as `ID_QUOTED`.
commit_hash:f5850228a3191ab84e3740fc1c36cf8882b08c40
|
|
|
|
|
|
|
| |
Before this patch we completed columns only at
SELECT projection. Now we complete it at these
constructions. Also it respects visibility rules.
commit_hash:aa1e6d4900e9b032801ddbf3bcd347750c2939b1
|
|
|
|
|
|
|
|
|
|
|
| |
Some refactorings to compact the code:
- YQL-19747: Pass TParsedInput to visitor
- YQL-19747: Add TParsedInput
- YQL-19747: Cosmetics
- YQL-19747: Refactor configuration
- YQL-19747: Refactor name to candidate mapping
commit_hash:44dfe7dc7bcc627ef9c20696077f2d962a3014f6
|
|
|
|
|
| |
Support `SELECT x.* FROM t AS x`.
commit_hash:64693f65281f385d6c0d3541fb2874b0153aa88c
|
|
|
|
|
|
|
|
|
|
|
| |
There was a problem with parsing a query like
`SELECT # FROM t`, as it parsed `FROM` as if it
is an expeceted column name, so we failed to parse
a table name after `FROM` and therefore can not
complete column names, while the are so useful at
this position. Also this hack improved parsing
other queries, according to changed tests.
commit_hash:f5a657022a164d1d4bbf906db4bd2ad67bbcd956
|
|
|
|
|
|
|
|
| |
Fixed a bug on self-join, as
table path was used as a key
to match columns with tables
instead of an alias.
commit_hash:0f9735a4c5ba0b2b88efc764bc5e7f5d41633fd8
|
|
|
|
| |
commit_hash:40a2de243a67135e44505619fb766954ba24e2e8
|
|
|
|
|
|
|
| |
Collect tables with aliases during global
analysis and send a multiple requests
to a schema provider.
commit_hash:51cbc40cee6cda09d5bfe256a0425e7c809c04f5
|
|
|
|
|
|
|
|
| |
Set `TCandidate::Shift` for functions and generic
types. So now brackets are balanced and UI should
adopt it. YDB CLI is ready for the update and just
cut off symbols after an expected cursor position.
commit_hash:9efc1110869af7be618b841c6c132572b61046a1
|
|
|
|
|
|
|
| |
Bug was that titlecase columns are not completed
on lowercase prefix, e.g. `SELECT a# FROM x`,
where `x = {Age}`.
commit_hash:e48f73176e94bcf16671af56d232450e368c9909
|
|
|
|
| |
commit_hash:70eea6b3e17f4aafae5eadb49724ba9036a55372
|
|
|
|
| |
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: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: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 <vvvv@yandex-team.com>
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
|
|
|
|
|
|
|
|
|
|
|
| |
---
- 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
commit_hash:6b048925e9cf8eede1e184503d43f211b3be6dbd
|