-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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 "Allow bigint to be used as time column in Presto" #7670
Closed
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
* Fix logo / branding files SVG was busted in the branding folder. Files were partly corrupt. This takes back the original logo, and offers a with-Apache and without-Apache option. SVG renders nicely. The pngs are also bigger. * add ASF license
* Remove ASF license from github templates (PR and issues) It shows as people open issues and PRs and it's confusing... * add to rat-excludes
…6964) * direct display for pre-selected tab * update parents * add AnchorLink component * add unit tests
* [SQL Lab] fix table metadata loading spinner The loading spinner used to be close to the new table name that was just added, and recently flickers and disappears early. This puts the spinner where it's expected to be. * Use class * Addressing comments * adapt CSS * add missing license
* chore: add bot config files and update issue templates * fix: exclude SIP
* fix: make SIPs exempt from stale bots * update pr template
* left align, close to button it's related to * text-muted, so it's a bit more subtle * fix required func props, where no func it actually passed
* [WiP] debugging and improving 'Time Table' closes #6948 * Lint * Remove passing down props from CollectionControl * Declarative passthrough of props * remove console.error
* Add all database access permission to 'Alpha' role * Grant all database access to Alpha
THEN is also a keyword in SQL
* [load_examples] download data at runtime When running `superset load_examples` to load example data sets, Superset used to load from the local package. This created a few issues notably around licensing (what are these datasets licensed as?) and around package size. For now, I moved the data sets here: https://github.com/apache-superset/examples-data Altered the logic to download the data from where it is stored. * flakes
* feat: bump superset-ui versions to 0.11 * fix: update version number again * fix: package-lock.json * test: disable large number test * fix: revert cors
* Adding permission for can_only_access_owned_queries * Fixing lint adding typing to variable * Adding test for queryview and enabling /queryview/api/read * Fixing issues with python typing
* fix: SqlaColumn.type overflow on mysql Hitting a new error when loading examples around a datatype that exceeds the 32 chars limit on SqlaColumn.type Type includes the 'COLLATE utf8mb4_general_ci' suffix which is too verbose and not needed in that context. * fix tests
…ith single value setting (#7494)
* Adding codecov targets and thresholds * Changing diff coverage rules to 1% threshold * Changing codecov threshold to 0 and removing ignore
* Fix colors in ellipsis * Change method name to align with convention * Fix js lint
* Add Filter on DatabaseView that filters DBs Based on Role Access * Update with mistercrunch's feedback
mistercrunch
approved these changes
Jun 7, 2019
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.
I agree here, seen it both ways so much I couldn't tell which one is more common...
* Add new escape characters to OnPasteSelect * Add Unit Tests to onPasteSelect_spec * Update new line to tab escape character * Fix indentation in 2 cases
* Apply dashboardFilter to dashboards * added missing comma
* Refactor db_engine_specs into package * Rename bigquery class and add epoch funcs * Fix flake8 errors * Dynamically load all engine specs * Fix linting errors and unit tests * Implement Snowflake epoch time funcs * Implement Teradata epoch time func * Fix presto datasource query and remove unused import * Fix broken datasource query * Add mypy ignore for false positive * Add missing license files * Make create_time_grains_tuple public * Fix flake8 quote * Fix incorrect licence header
john-bodley
force-pushed
the
revert-7218-VIZ-414
branch
from
June 8, 2019 22:30
c1bbe29
to
b1cb742
Compare
john-bodley
pushed a commit
to john-bodley/superset
that referenced
this pull request
Jun 8, 2019
john-bodley
added a commit
that referenced
this pull request
Jun 10, 2019
cccs-rc
pushed a commit
to CybercentreCanada/superset
that referenced
this pull request
Mar 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Per #7218 (comment) including a
BIGINT
column type as a time column in Presto is problematic as it could represent either a Unix time in seconds or milliseconds.The current correct way to handle Unix time columns is to set the
python_date_format
as eitherepoch
orepoch_ms
(depending on the encoding) which results in queries comprising the correct fidelity:Note #7656 plans to auto-detect the encoding of temporal columns.
to: @betodealmeida @mistercrunch