mosescha1972 opened a new issue, #37608: URL: https://github.com/apache/superset/issues/37608
### Bug description Title Box Plot shows incorrect date (e.g., 8959-12-31) when using Oracle DATE column as temporal field Summary When using an Oracle DATE column as the temporal field in a Superset Box Plot, the chart displays incorrect future dates such as 8959-12-31. This happens even though the column is correctly recognized as DATE and marked as Is temporal in the dataset. Environment Apache Superset (latest master as of recent build) Oracle 19c Dataset based on Oracle table with a DATE column (e.g., TRD_DT) Steps to Reproduce Create a dataset from an Oracle table where TRD_DT is of type DATE. In Dataset → Columns, mark TRD_DT as Is temporal. Create a Box Plot chart. Set: Time Grain = Day Time Range = Last 2 years Observe the X-axis dates. Actual Result The chart shows incorrect dates such as 8959-12-31 instead of the real trading dates. Expected Result The chart should display the actual values of TRD_DT correctly on the time axis. Root Cause Analysis Superset internally converts temporal fields to epoch milliseconds for Box Plot grouping. When the source column is Oracle DATE, Superset misinterprets the value as a numeric epoch value rather than a true datetime, resulting in extreme future dates. This issue does not appear in Line Charts or other time series charts, but is reproducible specifically in Box Plot, likely due to different internal time handling logic. Workaround Create a virtual column in the dataset: CAST(TRD_DT AS TIMESTAMP) Mark this new column as Is temporal and use it instead of the original DATE column. After this change, the Box Plot renders correct dates. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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]
