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

Can't select system keyspace from keyspaces dropdown menu #41

Closed
yadkov opened this issue Nov 8, 2022 · 10 comments
Closed

Can't select system keyspace from keyspaces dropdown menu #41

yadkov opened this issue Nov 8, 2022 · 10 comments
Assignees

Comments

@yadkov
Copy link

yadkov commented Nov 8, 2022

While creating queries in builder mode from Grafana to Astradb I can't select the system keyspace from keyspaces dropdown menu.

When I switch to code mode I am able to select from the system keyspace.

Grafana version: 8.5.13
Astradb plugin version: 0.2.1

@ktw4071 ktw4071 self-assigned this Nov 8, 2022
@ktw4071
Copy link
Contributor

ktw4071 commented Nov 8, 2022

Hi @yadkov,
Could you kindly upload UI screenshot that I can refer to? I will reproduce and fix it.
Thanks

@yadkov
Copy link
Author

yadkov commented Nov 9, 2022

This is the builder mode:
image

This is from the code mode:
image

@yadkov
Copy link
Author

yadkov commented Dec 19, 2022

Any updates?

@ktw4071
Copy link
Contributor

ktw4071 commented Dec 19, 2022

Hello @yadkov, been working with other work. If it's not an urgent issue, I will pick up after finishing my current work.

@scottlepp
Copy link
Contributor

Hi @yadkov we intentionally filter out system keyspaces since these are system generated tables.

Can you please help understand the use case of why you want to query these? Thanks.

@yadkov
Copy link
Author

yadkov commented Jan 4, 2023

We would like to monitor the partions counts and their corresponding size. In order to do this we need the data which is stored in size_estimates in the system keyspace.

@scottlepp
Copy link
Contributor

@yadkov thanks for the update. This seems like a more admin/advanced use case where the user knows the schema/metadata and how to write the CQL to get it, and has access to system tables.

The query builder is really meant for users who are not familiar with CQL and shouldn't see system tables, but I suppose this can be managed with permissions in Cassandra.

With your scenario, the user would rather use the query builder ui rather than just writing the CQL?

@yadkov
Copy link
Author

yadkov commented Jan 5, 2023

CQL is preferred.

@scottlepp
Copy link
Contributor

Then it seems accessing system tables from the query builder ui is not necessary. Going to close this.

@yadkov
Copy link
Author

yadkov commented Jan 6, 2023

Maybe a comment comment in the documentation about the system keyspace could be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants