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

Revert "Autocomplete in the table browser in SQL lab is broken (#7736)" #7743

Merged
merged 2 commits into from
Jun 21, 2019

Conversation

khtruong
Copy link
Contributor

@khtruong khtruong commented Jun 20, 2019

Accidentally broke connecting to tables after searching. Reverting this change.

This reverts commit d1b81e0.

REVIEWERS

@betodealmeida @DiggidyDave @xtinec

@betodealmeida
Copy link
Member

+1

@betodealmeida
Copy link
Member

betodealmeida commented Jun 20, 2019

Looks like the backend should return the tables in a standardized format, and it's not?

Copy link
Member

@etr2460 etr2460 left a comment

Choose a reason for hiding this comment

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

Lgtm

@codecov-io
Copy link

codecov-io commented Jun 21, 2019

Codecov Report

Merging #7743 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #7743      +/-   ##
==========================================
- Coverage   65.78%   65.75%   -0.03%     
==========================================
  Files         459      459              
  Lines       21925    21924       -1     
  Branches     2410     2410              
==========================================
- Hits        14424    14417       -7     
- Misses       7380     7386       +6     
  Partials      121      121
Impacted Files Coverage Δ
superset/assets/src/components/TableSelector.jsx 84.67% <100%> (-0.13%) ⬇️
superset/db_engine_specs/sqlite.py 45.83% <0%> (-20.84%) ⬇️
superset/utils/core.py 87.93% <0%> (-0.18%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1b81e0...9cde95e. Read the comment docs.

@betodealmeida betodealmeida merged commit 17c4b72 into apache:master Jun 21, 2019
@villebro
Copy link
Member

I believe the observed bug has its origins in changes introduced by #7453, which changes table names from strings to dicts/objects:

  • Before: tables were strings of format 'my_table' or 'my_schema.my_table'
  • Now: { schema: 'my_schema', table: 'my_table' }

The change was done because many engines support periods in the object names, which confused the frontend. However, apparently there were side-effects that were not covered by unit tests. If having tables in object format causes problems, one solution could be to make them strings again, but make sure periods in object names are properly escaped.

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

Successfully merging this pull request may close these issues.

5 participants