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

fix: Removing the logic to add timeseries_limit_metric to the data for table #9832

Merged

Conversation

michellethomas
Copy link
Contributor

@michellethomas michellethomas commented May 18, 2020

SUMMARY

Removing logic to add the timeseries_limit_metric to data for Table viz. This was previously necessary in the old Table viz to fix a bug where labeled metrics with a sortby wouldn't show up. This is no longer necessary in the new Table viz and causes an extra column to show up on the table.

TEST PLAN

Testing table viz with and without sortby, with and without labeled metrics.

ADDITIONAL INFORMATION

  • Has associated issue:
  • Changes UI
  • Requires DB Migration.
  • Confirm DB Migration upgrade and downgrade tested.
  • Introduces new feature or API
  • Removes existing feature or API

@john-bodley @etr2460 @ktmud

@michellethomas michellethomas changed the title Removing the logic to add timeseries_limit_metric to the data for table Fix: Removing the logic to add timeseries_limit_metric to the data for table May 18, 2020
@michellethomas michellethomas changed the title Fix: Removing the logic to add timeseries_limit_metric to the data for table fix: Removing the logic to add timeseries_limit_metric to the data for table May 18, 2020
Copy link
Member

@john-bodley john-bodley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add a check in a/the unit test to ensure the column count is correct to help prevent future regressions?

@michellethomas
Copy link
Contributor Author

@john-bodley the unit test that's there should prevent the time series table column from showing up in the data that gets returned, it was just written originally to return it because that was needed for the frontend.

I think this should have an integration test to make sure that when there's a metric and a sortby on a table, only the metric column shows up, that would have caught this bug when the table viz changed. When I looked into this, I noticed that the visualization integration tests were not actually running. Are you ok if I add the test in a separate PR after the visualization tests are turned back on?

@john-bodley john-bodley merged commit 368c85d into apache:master May 20, 2020
john-bodley pushed a commit to airbnb/superset-fork that referenced this pull request May 20, 2020
…r table (apache#9832)

* Removing the logic to add timeseries_limit_metric to the data for table viz

* Also make the change in viz_sip_38

* Fix tests

Co-authored-by: michelle_thomas <michelle.thomas@airbnb.com>
(cherry picked from commit 368c85d)
auxten pushed a commit to auxten/incubator-superset that referenced this pull request Nov 20, 2020
…r table (apache#9832)

* Removing the logic to add timeseries_limit_metric to the data for table viz

* Also make the change in viz_sip_38

* Fix tests

Co-authored-by: michelle_thomas <michelle.thomas@airbnb.com>
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 0.37.0 labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/S 🚢 0.37.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants