Improve the UX of SYSTEM INSTRUMENT ADD/REMOVE#93345
Improve the UX of SYSTEM INSTRUMENT ADD/REMOVE#93345pamarcos merged 7 commits intoClickHouse:masterfrom
Conversation
|
Workflow [PR], commit [eeedd36] Summary: ❌
|
Update doc after ClickHouse/ClickHouse#93345 syntax update
6299407
Backport #93345 to 25.12: Improve the UX of SYSTEM INSTRUMENT ADD/REMOVE
|
Patching all functions that match broke the tests in private. The CI didn't catch it because the Turns out in private when adding an instrumentation point for I'm going to tune the logic a little bit in a following PR to avoid matching the function name if it's within the template arguments to avoid this sort of inconveniences in the future. |
|
Hi @pamarcos @alexey-milovidov — while reviewing this PR I found the following:
Happy to discuss — close anything that's wrong or already addressed. |
Follow-up on #89173 based on this and this comments:
Improve the UX of SYSTEM INSTRUMENT ADD/REMOVE:
REMOVE. This is a nice to have thing, but previously could be done with a subqueryChangelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Improve the UX of SYSTEM INSTRUMENT ADD/REMOVE: use String literals for function names, patch all functions that match and allow using function_name in
REMOVEDocumentation entry for user-facing changes