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

[mixed time-series] collection of related issues #18236

Closed
3 tasks done
rumbin opened this issue Jan 31, 2022 · 4 comments
Closed
3 tasks done

[mixed time-series] collection of related issues #18236

rumbin opened this issue Jan 31, 2022 · 4 comments
Labels
#bug Bug report

Comments

@rumbin
Copy link
Contributor

rumbin commented Jan 31, 2022

This is a issue collection which bundles the various open issues that the Mixed Time-Series chart is currenlty exhibiting.

I am hoping that this compilation helps bundling the development efforts for this otherwise great chart type.
Presumably, some of these issues can be fixed in a single PR.
Thus, I'll try to categorize these issues a bit...

Note:
Some of the issues are also related to "Time-series Bar Chart v2"

Two queries

These issues arise from the fact that this chart type is building on two distict queries, Query A and Query B.
It seems that other Superset components are not handlich this circumstance gracefully:

Axes

X-Axis

Values formatting

Second Y-Axis

Environment

  • browser type and version: Chrome 96.0.4664.93
  • superset version: 1.4.0
  • all other versions: as defined in Superset's Docker image
  • Feature flags:
# stable:
      "THUMBNAILS": True,
      "SQLLAB_BACKEND_PERSISTENCE": True,
      "ENABLE_TEMPLATE_PROCESSING": True,
      "DASHBOARD_CROSS_FILTERS": True,

      # experimental:
      "ALERT_REPORTS": True,
      "ALERTS_ATTACH_REPORTS": True,
      "DASHBOARD_NATIVE_FILTERS": True,

      # unclassified:
      "ENABLE_EXPLORE_DRAG_AND_DROP": True,
      "ENABLE_DND_WITH_CLICK_UX": True,

      # development:
      "DASHBOARD_NATIVE_FILTERS_SET": True

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are 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.
@rumbin rumbin added the #bug Bug report label Jan 31, 2022
@stale
Copy link

stale bot commented Apr 17, 2022

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 17, 2022
@rumbin
Copy link
Contributor Author

rumbin commented Apr 17, 2022

This issue should not be closed by the stale bot, in my eyes.

@stale stale bot removed the inactive Inactive for >= 30 days label Apr 17, 2022
@huyhandes
Copy link

1 upvote, still not fixed I think

@rusackas
Copy link
Member

Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering any of these issues, can we file separate issues for each item that needs to be addressed? That'll help make sure items get tackled and closed more expediently.

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

No branches or pull requests

3 participants