-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Conversation
@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? |
e942a2c
to
de5c8d9
Compare
de5c8d9
to
32a4850
Compare
Codecov Report
@@ 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
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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? |
@lyndsiWilliams per you comment,
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 😁 |
@eschutho Container image not yet published for this PR. Please try again when build is complete. |
@eschutho Ephemeral environment creation failed. Please check the Actions logs for details. |
@john-bodley any news? |
@john-bodley Can you add in description |
Remove unused variable for CI to pass
/testenv up |
@lyndsiWilliams Container image not yet published for this PR. Please try again when build is complete. |
@lyndsiWilliams Ephemeral environment creation failed. Please check the Actions logs for details. |
There was a problem hiding this 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?
/testenv up |
@EugeneTorap Ephemeral environment creation is currently limited to committers. |
/testenv up |
@lyndsiWilliams Ephemeral environment spinning up at http://35.90.233.189:8080. Credentials are |
I tested SQL lab in the ephemeral and tables are loading now. |
Can we merge it? |
LGTM! |
Ephemeral environment shutdown and build artifacts deleted. |
Can someone explain to me how I can carry out the execution of this command? |
Co-authored-by: Elizabeth Thompson <eschutho@gmail.com> (cherry picked from commit 8c16806)
)" This reverts commit 8c16806.
@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. |
SUMMARY
Addresses regression introduced in #21284.
cc: @EugeneTorap
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
AFTER
TESTING INSTRUCTIONS
CI and verified the table selector worked in various surfaces.
ADDITIONAL INFORMATION