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: Address regression introduced in #21284 #21470

Merged
merged 2 commits into from
Sep 16, 2022

Conversation

john-bodley
Copy link
Member

@john-bodley john-bodley commented Sep 14, 2022

SUMMARY

Addresses regression introduced in #21284.

cc: @EugeneTorap

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

AFTER

Screen Shot 2022-09-14 at 11 22 08 AM

Screen Shot 2022-09-14 at 11 17 46 AM

Screen Shot 2022-09-14 at 11 16 17 AM

TESTING INSTRUCTIONS

CI and verified the table selector worked in various surfaces.

ADDITIONAL INFORMATION

  • Has associated issue: Fixes always return with this error. ["There was an error loading the tables"] #21476
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@john-bodley
Copy link
Member Author

@eschutho, @lyndsiWilliams, and @pkdotson per #21075 it seems there's a new dataset selector which uses server side searching which was disabled in #21284. Is this actually a requirement for these new components or is it possible to remove said logic?

@john-bodley john-bodley marked this pull request as ready for review September 14, 2022 20:34
@john-bodley john-bodley force-pushed the john-bodley--fix-21284 branch from e942a2c to de5c8d9 Compare September 14, 2022 20:35
@john-bodley john-bodley force-pushed the john-bodley--fix-21284 branch from de5c8d9 to 32a4850 Compare September 14, 2022 20:37
@codecov
Copy link

codecov bot commented Sep 14, 2022

Codecov Report

Merging #21470 (33388ad) into master (59ca786) will increase coverage by 0.09%.
The diff coverage is 80.74%.

❗ Current head 33388ad differs from pull request most recent head a6209a4. Consider uploading reports for the commit a6209a4 to get more accurate results

@@            Coverage Diff             @@
##           master   #21470      +/-   ##
==========================================
+ Coverage   66.59%   66.69%   +0.09%     
==========================================
  Files        1791     1793       +2     
  Lines       68555    68490      -65     
  Branches     7319     7275      -44     
==========================================
+ Hits        45654    45676      +22     
+ Misses      21008    20946      -62     
+ Partials     1893     1868      -25     
Flag Coverage Δ
javascript 52.87% <75.62%> (+0.10%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...d/packages/superset-ui-chart-controls/src/index.ts 100.00% <ø> (ø)
...et-ui-chart-controls/src/shared-controls/index.tsx 59.61% <0.00%> (+11.17%) ⬆️
...d/packages/superset-ui-chart-controls/src/types.ts 100.00% <ø> (ø)
...i-chart-controls/src/utils/expandControlConfig.tsx 100.00% <ø> (ø)
.../superset-ui-core/src/query/normalizeTimeColumn.ts 100.00% <ø> (ø)
...s/legacy-plugin-chart-heatmap/src/controlPanel.tsx 57.14% <ø> (ø)
...ns/legacy-plugin-chart-map-box/src/controlPanel.ts 30.00% <ø> (ø)
...t-chart-deckgl/src/utilities/sharedDndControls.jsx 100.00% <ø> (ø)
...s/legacy-preset-chart-nvd3/src/Bar/controlPanel.ts 14.28% <ø> (ø)
...charts/src/Timeseries/Regular/Bar/controlPanel.tsx 31.25% <ø> (ø)
... and 46 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@lyndsiWilliams
Copy link
Member

@eschutho, @lyndsiWilliams, and @pkdotson per #21075 it seems there's a new dataset selector which uses server side searching which was disabled in #21284. Is this actually a requirement for these new components or is it possible to remove said logic?

There are actually pre-existing instances of paginated searching elsewhere in SQL Lab. Bringing this search functionality to the front end could get really expensive, could we re-enable server side searching?

@john-bodley
Copy link
Member Author

john-bodley commented Sep 14, 2022

@lyndsiWilliams per you comment,

There are actually pre-existing instances of paginated searching elsewhere in SQL Lab. Bringing this search functionality to the front end could get really expensive, could we re-enable server side searching?

could you elaborate where this is used? Also when we (Airbnb) tried using the backend search functionality—augmenting our local environment—for fetching tables names we noticed the latency was unacceptable.

cc: @justinpark

@lyndsiWilliams
Copy link
Member

lyndsiWilliams commented Sep 14, 2022

@lyndsiWilliams per you comment,

There are actually pre-existing instances of paginated searching elsewhere in SQL Lab. Bringing this search functionality to the front end could get really expensive, could we re-enable server side searching?

could you elaborate where this is used? Also when we (Airbnb) tried using the backend search functionality—augmenting our local environment—for fetching tables names we noticed the latency was unacceptable.

cc: @justinpark

I looked into this further and discussed with Elizabeth, we actually don't use server side searching for this and it isn't used elsewhere in SQL Lab like I thought. The table data isn't stored in our database, we fetch it from their db and it's a "reflection" of their database, not actually scanning rows in a database.

It should be fine to remove the server side searching after all 😁

@github-actions
Copy link
Contributor

@eschutho Container image not yet published for this PR. Please try again when build is complete.

@github-actions
Copy link
Contributor

@eschutho Ephemeral environment creation failed. Please check the Actions logs for details.

@EugeneTorap
Copy link
Contributor

EugeneTorap commented Sep 16, 2022

@john-bodley any news?
FYI we have /testenv up command to deploy test ENV and then you can ping @jinghua-qa and @andrey-zayats to test it to avoid the regression bugs.

@EugeneTorap
Copy link
Contributor

EugeneTorap commented Sep 16, 2022

@john-bodley Can you add in description Fix #21476 to auto close the issue after merging it?

Remove unused variable for CI to pass
@lyndsiWilliams
Copy link
Member

/testenv up

@github-actions
Copy link
Contributor

@lyndsiWilliams Container image not yet published for this PR. Please try again when build is complete.

@github-actions
Copy link
Contributor

@lyndsiWilliams Ephemeral environment creation failed. Please check the Actions logs for details.

Copy link
Member

@lyndsiWilliams lyndsiWilliams left a comment

Choose a reason for hiding this comment

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

LGTM! @jinghua-qa could you take a look at the ephemeral once it's up and make sure all tables are loading correctly now?

@lyndsiWilliams lyndsiWilliams added the need:qa-review Requires QA review label Sep 16, 2022
@EugeneTorap
Copy link
Contributor

/testenv up

@github-actions
Copy link
Contributor

@EugeneTorap Ephemeral environment creation is currently limited to committers.

@lyndsiWilliams
Copy link
Member

/testenv up

@github-actions
Copy link
Contributor

@lyndsiWilliams Ephemeral environment spinning up at http://35.90.233.189:8080. Credentials are admin/admin. Please allow several minutes for bootstrapping and startup.

@eschutho
Copy link
Member

I tested SQL lab in the ephemeral and tables are loading now.

@EugeneTorap
Copy link
Contributor

Can we merge it?

@jinghua-qa
Copy link
Member

LGTM!

@eschutho eschutho merged commit 8c16806 into apache:master Sep 16, 2022
@github-actions
Copy link
Contributor

Ephemeral environment shutdown and build artifacts deleted.

@bumasl
Copy link

bumasl commented Sep 17, 2022

/testenv up

Can someone explain to me how I can carry out the execution of this command?

jinghua-qa pushed a commit to preset-io/superset that referenced this pull request Sep 19, 2022
Co-authored-by: Elizabeth Thompson <eschutho@gmail.com>
(cherry picked from commit 8c16806)
mayurnewase added a commit to mayurnewase/incubator-superset that referenced this pull request Sep 22, 2022
@eschutho
Copy link
Member

@bumasl only Superset committers have permissions to create test environments. But you can request that someone start one for you if you'd like to test.

@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 2.1.0 labels Mar 13, 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 need:qa-review Requires QA review size/M 🚢 2.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

always return with this error. ["There was an error loading the tables"]
7 participants