Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When many tables under a DB, dashboard keyvis feature will cost a lot of resource #54281

Closed
Tracked by #50959
lance6716 opened this issue Jun 27, 2024 · 2 comments · Fixed by #54608
Closed
Tracked by #50959

When many tables under a DB, dashboard keyvis feature will cost a lot of resource #54281

lance6716 opened this issue Jun 27, 2024 · 2 comments · Fixed by #54608
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@lance6716
Copy link
Contributor

Enhancement

img_v3_02c6_a75c806e-3a46-40ba-bdad-3cc752158b0g

@lance6716 lance6716 added the type/enhancement The issue or PR belongs to an enhancement. label Jun 27, 2024
@D3Hunter
Copy link
Contributor

D3Hunter commented Jul 8, 2024

also see the quote in #54391 (comment)

@lance6716
Copy link
Contributor Author

also see the quote in #54391 (comment)

To be clarify, the single table ID query pattern is /db-table/{tableID}, it's not /db-table?table_id=xxx. And I see a simliar endpoint in the stack overflow answers /db-table/{tableID,...}.

So for now we have three candicate

  • /db-table/{tableID,...}
  • /db-table?table_ids={tableID,...}
  • /db-table?table_id={tableID}&table_id={tableID}

I'll think about them later. cc @mornyx @easonn7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
2 participants