-
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
feat(datasource): Checkbox for always filtering main dttm in datasource #25204
feat(datasource): Checkbox for always filtering main dttm in datasource #25204
Conversation
@eschutho Hi! Should that checkbox be in the database connection? Or it need to be in the dataset settings. |
superset-frontend/src/components/Datasource/DatasourceEditor.jsx
Outdated
Show resolved
Hide resolved
superset-frontend/src/components/Datasource/DatasourceEditor.jsx
Outdated
Show resolved
Hide resolved
@Always-prog this looks like good to me here in the dataset editor, but it wouldn't work for all databases, is that right? |
Co-authored-by: Elizabeth Thompson <[email protected]>
Co-authored-by: Elizabeth Thompson <[email protected]>
@eschutho Currently this feature will works for all databases if checkbox is checked, and I think it's ok. |
Suggestion on the text:
Should we call the field "Secondary Time Column" or "Secondary Datetime Column" to match "Default Datetime" in the datasets? |
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 is awesome, I think it's a better approach. I left a few comments, and also, can you add a unit test showing the query that is generated when the column is on vs. off?
superset-frontend/src/components/Datasource/DatasourceEditor.jsx
Outdated
Show resolved
Hide resolved
@betodealmeida Done, I added unit test and fixed name of the checkbox. |
@Always-prog This commit looks more like a feature. Could you change the title from fix to feat? |
@justinpark Done |
@eschutho @betodealmeida Hi! |
@eschutho Hi! If PR is ok, can I get merge :P? |
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 is awesome!
…ce (apache#25204) Co-authored-by: Elizabeth Thompson <[email protected]>
…ce (apache#25204) Co-authored-by: Elizabeth Thompson <[email protected]>
…ce (apache#25204) Co-authored-by: Elizabeth Thompson <[email protected]>
SUMMARY
Fixes #22223.
There a feature in Superset that permanently adds a second time column to requests to Clickhouse, ElasticSearch, Kusto. But there is an problem with it, as many people think it's a bug :).
How about adding a checkbox for feature time secondary column to the dataset? i think it would be better than hardcoding it for all database connections (Clickhouse, elasticsearch, Kusto). It would also allow the ability to add a second time column to other databases. This PR doing it!
SCREENSHOTS
Here is how it looks for user
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION