Tests for Monitoring Endpoints - Level Database#1
Open
SergeyNs-45 wants to merge 529 commits into
Open
Conversation
Co-authored-by: Roman Kuzin <kuzin57@yandex-team.ru>
Мы делаем минимальную версию кластера с replication factor 1, чтобы внешние юзеры могли развернуть кластер для тестирования функциональности на минимуме ресурсов на одной машике с одной датанодой. Необходимость этих фиксов всплыла, когда я заметил, что YQL запрос при подготовке операции грузит в Кипарис различные файлы – .so-шки с библиотеками, mrjob и прочее. Все это грузилось с дефолтными константами rf, сделал так, чтобы их можно было переопределить. * Changelog entry Type: feature Component: cpp-sdk make option `file_cache_replication_factor` dynamic commit_hash:900ea0d6483926e7a444c5b593cf661544744590
commit_hash:b65593ded662ce917f6ab88932637ce25697a544
commit_hash:6f0673a811bccd241c54f82ea1ebb61bc75d7511
Co-authored-by: Roman Kuzin <kuzin57@yandex-team.ru>
Co-authored-by: Velikhov Pavel <pavelvelikhov@localhost.localdomain>
…late progress of fulltext index in proper way. (ydb-platform#36518)
commit_hash:bbe203792d3ea7883da2aacbce376bf5355a2283
commit_hash:2680ca1b2b87c9de6fd39a3bf31fedb23cdd2871
commit_hash:82780e11501fbf21e1f92f96707dc94ccbebc9c2
commit_hash:5e2a2254279501ad2bde571fbd53c1a27a00e898
commit_hash:af85d51f21805a09d64bfe1dc0899efcac5c61b2
…orm#36369) Remove expensive Grab* copies from `TSplitMerge::Propose()`. `TSplitMerge::Propose()` called `TMemoryChanges::Grab*` to deep-copy `TTableInfo`, `TSubDomainInfo`, and `TPathElement` on every split/merge. These copies support aborting suboperation `Propose()` phase (`UnDo()` rollback via `AbortOperationPropose()`), but `TSplitMerge` never fails by itself and never combines with other scheme suboperations (no other suboperation's fail can trigger `TSplitMerge`'s abort), so AbortPropose path can never happen for `TSplitMerge`. The copies were always wasted.
One more GPU arch + correct setting of family flags https://docs.nvidia.com/cuda/archive/12.9.0/cuda-toolkit-release-notes/index.html commit_hash:9e33d59c8f3870034614b4855afbf4dcfeeb96d1
commit_hash:0f059bb0c9f0fc8f8a5d77147b6c4d5ad8d9cf22
commit_hash:fa698b11f2fd926eb90c0fb5952038aa0da30b8f
commit_hash:fbe0a55793035b0a53b7167e7b3fefae58cd716b
commit_hash:75d17196a7f2534fa92835a6477e72e59a136ea7
commit_hash:c6aef447a589e761372dc7008458b23a60c4d3f6
commit_hash:e850d2be6420037cce88f2d0c82cc7531b77d7a0
Co-authored-by: Sergei Novikov <jmvssnovikov@10.208.95.10-red.dhcp.yndx.net>
Co-authored-by: Roman Kuzin <kuzin57@yandex-team.ru>
…6963) Co-authored-by: Roman Kuzin <kuzin57@yandex-team.ru>
… and JSON payloads. Refactor _test_endpoint and _test_endpoints functions to accommodate these changes, and introduce _test_endpoints_with_payloads for POST requests. Update tests for node proxy monitoring and database endpoints to reflect new functionality.
- Introduced `viewer_database_query_gate` to enforce explicit database queries for certain viewer paths. - Updated `viewer_content.h` and `viewer_tabletcounters.h` to handle missing parameters with appropriate error responses. - Enhanced `viewer.cpp` to evaluate database query requirements before processing requests. - Added tests for new database query requirements in `test_mon_endpoints_auth.py` to ensure proper access control. - Updated `ya.make` to include new source files for the database query gate functionality.
- Modified the constant `VIEWER_JSON_PATHS_REQUIRING_EXPLICIT_DATABASE_QUERY` to reflect the updated path list in `test_mon_endpoints_auth.DATABASE_ENDPOINTS_LIST`. - Removed outdated paths to ensure consistency with the current testing framework.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog category
Description for reviewers
Fixes ydb-platform#35956