-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: the TableDetails, TableStats, DatabaseDetails API don't decode with a proper tenant prefix #82879
Copy link
Copy link
Closed
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyA-server-architectureRelates to the internal APIs and src org for server codeRelates to the internal APIs and src org for server codeC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Description
Describe the problem
The code for these HTTP API handlers all use generateTableSpans(), which internally uses keys.TODOSQLCodec.
This is incorrect.
The helper function should instead receive the codec as argument, and the HTTP API handler should pass the ambient codec (the current one for the tenant) instead.
Expected behavior
Code path is tenant-agnostic and does not use keys.TODOSQLCodec.
Epic: CRDB-16704
Jira issue: CRDB-16705
SQL-O11Y Endpoint Migration Tracking Issue: #89429
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyA-server-architectureRelates to the internal APIs and src org for server codeRelates to the internal APIs and src org for server codeC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.