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

"Custom" dimensions in Druid datasources cause problems with some Visualization types #4805

Closed
3 tasks done
lrcutra opened this issue Apr 11, 2018 · 4 comments
Closed
3 tasks done
Labels
inactive Inactive for >= 30 days

Comments

@lrcutra
Copy link

lrcutra commented Apr 11, 2018

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

  • 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

0.24.0

All problems mentioned within this issue relate to Druid datasources.

Expected results

Superset should visualize the query when using user-defined dimension in Group-By clause.

Actual results

With some types of visualizations it's not possible to use custom dimensions (e.g. lookup, extractions [extractionFn of any kind]) in the Group-by clause.

Using a single custom dimension in Group-by with Visualization Type: "Distribution - Bar Chart", the result looks as follows:

Only the name of the dimension is displayed, but no visualization at all.

Adding at least one additional dimension (of any kind) solves the problem, and the visualization works.

However it remains impossible to use some types of visualizations when grouping by a single "custom" dimension.

Steps to reproduce

Add an individual dimension to your Druid datasource by specifying a custom json [e.g. lookup or extraction]. Use this dimension within the Group-By clause of your query with visualization type "Distribution-Bar chart".
Superset won't visualize but only return the name of the "custom" dimension.

@ghulands
Copy link

@lrcutra, you might want to cherry pick in this PR #4740 until it gets merged.

@stale
Copy link

stale bot commented Apr 10, 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 10, 2019
@lrcutra
Copy link
Author

lrcutra commented Apr 11, 2019 via email

@stale stale bot removed the inactive Inactive for >= 30 days label Apr 11, 2019
@stale
Copy link

stale bot commented Jun 10, 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 Jun 10, 2019
@stale stale bot closed this as completed Jun 17, 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