ytsaurus / ytsaurus/ytsaurus

AlterQuery makes query text unsearchable

Open
#1,532 0 comments 0 reactions 1 assignee Claimed by @Krisha11 View on GitHub
query tracker
Dominant language
C++
Stars
2.2k
Forks
219
PR merge metrics
No merged PRs in 30d

Description

This was tested on latest QueryTracker release: 0.0.11
```
➜ yt start-query yql 'select 4321'
bf4796ae-99f3edd5-4ce42a9c-b8249df2
➜ yt list-queries --filter '4321' | grep bf4796ae-99f3edd5-4ce42a9c-b8249df2
"id" = "bf4796ae-99f3edd5-4ce42a9c-b8249df2";
➜ yt alter-query --annotations '{}' bf4796ae-99f3edd5-4ce42a9c-b8249df2
➜ yt list-queries --filter '4321' | grep bf4796ae-99f3edd5-4ce42a9c-b8249df2
[Nothing here]
```

Most likely it happens in `main` as well
Most likely it is caused by NOT using update=true in WriteRows in AlterQuery. For example [here](https://github.com/ytsaurus/ytsaurus/blob/3947ecdc8902244019c06cb324590cc74a213339/yt/yt/server/query_tracker/query_tracker_proxy.cpp#L1368-L1371)
As a consequence, other fields may be set to null (like access control object from [this issue](https://github.com/ytsaurus/ytsaurus/issues/1083)(seems fixed in `main`))

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.