frafra opened a new issue #16870: URL: https://github.com/apache/superset/issues/16870
Apache Superset should not list `TIME` columns as `TIME COLUMNS` (that is how Superset describes `DATE`/`DATETIME`/`TIME` columns in the `Table` view), or a major rework to handle `TIME` columns properly should be done. Thus, a different issue/PR should be created for that. Setting a time range on such columns is useless at the moment. #### How to reproduce the bug 1. Go to a dataset containing a `TIME` column 2. Select a time range 3. Run ### Expected results Such time column should not have been an option, or time range should be able to work with time without a date. ### Actual results No results. ### Environment Latest Superset revision on Docker. ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [X] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [X] I have reproduced the issue with at least the latest released version of superset. - [X] I have checked the issue tracker for the same issue and I haven't found one similar. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
