ValentinC-BR opened a new issue #13702:
URL: https://github.com/apache/superset/issues/13702


   When using a calculated column as the TIME COLUMN, the preset filters 
(actually all the filters in the time section) do not work.
   The calculated field (date or datetime) is compared to a STRING, causing the 
SQL request not to work.
   
   ### Expected results
   
   The calculated column should be compared to a DATE or DATETIME value when 
the user applies a filter
   
   ### Actual results
   
   The calculated column is compared to a STRING value
   
   ### Screenshots
   
   TABLE CONFIGURATION
   
   
![image](https://user-images.githubusercontent.com/79460908/111745842-7767f500-888d-11eb-845f-52901a09d9a6.png)
   
   CHART CONFIGURATION
   
   
![image](https://user-images.githubusercontent.com/79460908/111745953-a1211c00-888d-11eb-8be7-de9e167b2457.png)
   
   GENERATED QUERY
   
   ![Capture d’écran 2021-03-19 à 08 33 
19](https://user-images.githubusercontent.com/79460908/111748238-8ef4ad00-8890-11eb-9ad5-2c8a812a6fb3.png)
   
   #### How to reproduce the bug
   
   1. Create a calculated column, with a date or datetime format
   2. Select it as THE time column
   3. Chose any time filter (last month for instance)
   4. RUN query
   
   
   ### Environment
   
   (please complete the following information):
   
   - superset version: 1.0.1
   - python version: 3.7.9
   - node.js version: doesn't apply, I run on Kubernetes, using gunicorn as 
server
   - source : Athena
   
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] 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.
   
   
   ### Additional context
   
   _None_
   


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to