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

Why we don't have other metrics but only the count(*) metric on metrics ? #5740

Closed
2 tasks
sowalassane opened this issue Aug 27, 2018 · 2 comments
Closed
2 tasks
Labels
inactive Inactive for >= 30 days

Comments

@sowalassane
Copy link

Make sure these boxes are checked before submitting your issue - thank you!

  • [x ] I have checked the superset logs for python stacktraces and included it here as text if any
  • I have reproduced the issue with at least the latest released version of superset
  • I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

Superset version 0.26.3

Expected results

Have all metrics that are present on my druid datasource

Actual results

Have only count(*) metric

Steps to reproduce

Hi all,
@mistercrunch
I create my druid datasource from hive tables and have more than one metric.
But in superset, i see only the count(*) metric as shown on the screenshot below:

image
I know that i can compute some aggregations as sum, max or min of the metrics but i need just the values without this aggregations .
What have i to do to have all metrics in the metrics ?

I am sorry if my questions are very basic, i am just new in superset.

Thanks in advance !

@sunnyKrystal
Copy link

@sowalassane
I suffered the same issue.
Maybe you can try to modified metric's SQL expression as below:
change COUNT(xxx) to COUNT(xxx)/1

or try to add metrics in this way #4736

@stale
Copy link

stale bot commented Apr 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 28, 2019
@stale stale bot closed this as completed May 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

2 participants