diff options
| author | vityaman <[email protected]> | 2025-04-28 17:50:31 +0300 |
|---|---|---|
| committer | robot-piglet <[email protected]> | 2025-04-28 18:13:27 +0300 |
| commit | f35bf94dbc72f06a35459f8d854866b83b9a49ea (patch) | |
| tree | b5afdcc946f4399860928e6a627fca041a69d91d /library/python/runtime_py3/test/test_traceback.py | |
| parent | 3dfd8d9b20fe8902588dc35edb24423fbf165917 (diff) | |
YQL-19747 Enable custom NameSet and FrequencyData
Clients might want to use custom `NameSet` and `FrequencyData` in their environment, for example, to get their private UDFs and to have more relevant ranking that includes their private UDF and respect their usage pattern.
To achieve this goal I decided to load pure `NameSet` and `FrequencyData` and provide functions for pruning. Also I checked defaults and decided that it is more common for a client to create a `StaticNameService` from pure `NameSet` and `FrequencyData` to keep their pruning consistent.
I also extracted a separate module `ranking`. It will be needed when I will implement `UnionNameService` to union `StaticNameService` and `SchemaNameService`. `UnionNameService` will load `Limit` names from each child and then crop them to sorted prefix of length `Limit` using `IRanking`.
---
- Related to `YQL-19747`
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/14
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1246
Co-authored-by: vvvv <[email protected]>
Co-authored-by: vvvv <[email protected]>
commit_hash:cdca301a58a34e56d537a447b4ff779cd70faea6
Diffstat (limited to 'library/python/runtime_py3/test/test_traceback.py')
0 files changed, 0 insertions, 0 deletions