samar-sajnani opened a new issue, #16788:
URL: https://github.com/apache/druid/issues/16788

   Interval is historical so the returned counts and values should be identical 
for two runs of the same query. However, when granularity with period and 
timezone is used in the query, the results may vary when a query is rerun.
   
   Granularity being used:
   
   ```
       "granularity": {
           "type": "period",
           "period": "P1D",
           "timeZone": "GB",
           "origin": "2024-06-01T00:00:00+01:00"
       },
   ```
   
   ### Affected Version
   
   29.0.1 and 0.22.0
   
   ### Description
   
   Please include as much detailed information about the problem as possible.
   - Cluster size
   26 historical, 2 hot-tier historicals, 6 middlemanagers, 7 query nodes, 2 
masters
   - Configurations in use
   [conf.zip](https://github.com/user-attachments/files/16357646/conf.zip)
   
   - Recreate issue:
   Run a query with period granularity, timezone and a period of P1D
   - No error messages
   
   Below are some examples of the problematic output.
   
   Some images of different runs of the same query with timezone, different 
counts and values on reruns every once in a while:
   
   <img width="1138" alt="Screenshot 2024-07-23 at 10 19 46 PM" 
src="https://github.com/user-attachments/assets/56bc8435-9704-476a-bfd1-35b797059028";>
   <img width="1134" alt="Screenshot 2024-07-23 at 10 22 02 PM" 
src="https://github.com/user-attachments/assets/6fdd03d7-64ea-4a23-8541-23cbc214f05f";>
   
   Some images of different runs with "day" as granularity instead, this 
provides the same count every time it's executed:
   <img width="1126" alt="Screenshot 2024-07-23 at 10 30 22 PM" 
src="https://github.com/user-attachments/assets/5b74a576-9550-4ff0-9636-7621ddca0a6a";>
   <img width="1136" alt="Screenshot 2024-07-23 at 10 28 26 PM" 
src="https://github.com/user-attachments/assets/06a34e7c-0e80-4048-81fa-0ca4950d7d17";>
   
   
   
   
   
   


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

Reply via email to