winglight opened a new issue, #22223:
URL: https://github.com/apache/superset/issues/22223

   A clear and concise description of what the bug is.
   
   #### How to reproduce the bug
   
   1. create a dataset from any ES index with temporal columns
   2. create a chart based on the dataset previous created and select TABLE mode
   3. check the default datetime column(let's say, default_date) of the 
dataset, and choose another temporal column(let's say, second_date) as time 
column 
   4. choose any TIME RANGE filter, such as previous calendar week and update 
chart
   5. click the right top button "..." and click the button "View query"
   6. in SQL, you'll see:
   ```
   WHERE default_date>= '2022-11-14 00:00:00.000000'
     AND default_date< '2022-11-21 00:00:00.000000'
     AND second_date>= '2022-11-14 00:00:00.000000'
     AND second_date< '2022-11-21 00:00:00.000000'
   ```
   As contrast, if the dataset comes from mysql, it works as expected. So, I 
certainly confirm that's a bug.
   
   ### Expected results
   
   The SQL should be:
   ```
   WHERE 
     AND second_date>= '2022-11-14 00:00:00.000000'
     AND second_date< '2022-11-21 00:00:00.000000'
   ```
   
   ### Actual results
   
   ```
   WHERE default_date>= '2022-11-14 00:00:00.000000'
     AND default_date< '2022-11-21 00:00:00.000000'
     AND second_date>= '2022-11-14 00:00:00.000000'
     AND second_date< '2022-11-21 00:00:00.000000'
   ```
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   
   ### Environment
   (please complete the following information):
   
   - browser type and version: chrome 107
   - superset version: `k8s helm chart version: 0.7.7 app version: 1.0`
   - python version: `3.8.13`
   - node.js version: `N/A`
   - any feature flags active:
   
   ### 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.
   - [☑️ ] I have reproduced the issue with at least the latest released 
version of superset.
   - [☑️] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   Add any other context about the problem here.
   


-- 
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: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to