-
Notifications
You must be signed in to change notification settings - Fork 14k
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
feat: method for dynamic allows_alias_in_select
#25882
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
betodealmeida
changed the title
feat: method for dynamic allows_alias_in_select
feat: method for dynamic Nov 6, 2023
allows_alias_in_select
betodealmeida
force-pushed
the
sc-76228
branch
from
November 6, 2023 22:50
dca55fb
to
491a2ce
Compare
betodealmeida
commented
Nov 6, 2023
@@ -765,7 +765,7 @@ def db_engine_spec(self) -> builtins.type["BaseEngineSpec"]: | |||
raise NotImplementedError() | |||
|
|||
@property | |||
def database(self) -> builtins.type["Database"]: |
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.
This was wrong, but was hidden by a bunch of # type: ignore
comments.
betodealmeida
force-pushed
the
sc-76228
branch
from
November 6, 2023 23:08
f9c6975
to
7f6b422
Compare
john-bodley
approved these changes
Nov 7, 2023
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
pushed a commit
to preset-io/superset
that referenced
this pull request
Nov 8, 2023
(cherry picked from commit 80caba3)
josedev-union
pushed a commit
to Ortege-xyz/studio
that referenced
this pull request
Jan 22, 2024
cccs-rc
pushed a commit
to CybercentreCanada/superset
that referenced
this pull request
Mar 6, 2024
mistercrunch
added
🏷️ bot
A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels
🚢 3.1.0
labels
Mar 8, 2024
sfirke
pushed a commit
to sfirke/superset
that referenced
this pull request
Mar 22, 2024
vinothkumar66
pushed a commit
to vinothkumar66/superset
that referenced
this pull request
Nov 11, 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
preset:2023.45
size/M
🚢 3.1.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
DB engine specs have an attribute called
allows_alias_in_select
, indicating if they support aliases inSELECT
statements. For Dremio, this attribute is version dependent — see the fix in their release notes.Because of that, we've been ping-ponging on the attribute. First I disabled it in #23872, and later it was re-enabled in #25657 when the fix came out. Since we have Superset users running older versions, I added a new class method
get_allows_alias_in_select
, that uses theversion
field in the database extra configuration.Note that this requires users running Dremio < 24.1.0 to explicitly add the
version
field when configuring their databases. I'm not sure if we could determine the version at runtime, but even if we could it would require us to run a pre-query every time, which is needlessly expensive.Also note that the
version
field is already used in Presto for version-dependent features.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N/A
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION