dosubot[bot] commented on issue #37608: URL: https://github.com/apache/superset/issues/37608#issuecomment-3834106111
<!-- Answer --> This is a known limitation in Superset's Box Plot chart when using Oracle DATE columns. The Box Plot plugin treats the x-axis as categorical and expects the backend to provide correctly-typed temporal values. If the Oracle DATE column isn't explicitly cast to TIMESTAMP, it can be misinterpreted as a numeric epoch, resulting in extreme future dates like 8959-12-31. Other chart types, like Line Chart, use a dedicated timeseries stack that normalizes and tags temporal fields, so they don't have this issue. The recommended workaround is to create a virtual column in your dataset using `CAST(TRD_DT AS TIMESTAMP)`, mark it as temporal, and use that column in your Box Plot. This ensures the date is recognized and formatted correctly by the chart plugin. This approach is consistent with maintainers' guidance for similar temporal data issues in Superset ([reference](https://github.com/apache/superset/issues/27798)). Let me know if you want more details on the technical differences in how Box Plot and other charts handle temporal fields. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1967ad56-0b11-4bb7-8032-e9cc2b852bd3?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20a%20known%20limitation%20in%20Superset%27s%20Box%20Plot%20chart%20when%20using%20Oracle%20DATE%20columns.%20The%20Box%20Plot%20plugin%20treats%20the%20x-axis%20as%20categorical%20and%20expects%20the%20backend%20to%20provide%20correctly-typed%20temporal%20values.%20If%20the%20Oracle%20DATE%20column%20isn%27t%20explicitly%20cast%20to%20TIMESTAMP%2C%20it%20can%20be%20misinterpreted%20as%20a%20numeric%20epoch%2C%20resulting%20in%20extreme%20future%20dates%20like%208959-12-31.%20Other%20chart%20types%2C%20like%20Line%20Chart%2C%20use%20a%20dedicated%20timeseries%20stack%20that%20normalizes%20and%20tags%20temporal%20fields%2C%20so%20they%20don%27t%20have%20this%20issue.%0A%0AThe%20recommended%20workaround%20is%20to%20create%20a%20virtual%20co lumn%20in%20your%20dataset%20using%20%60CAST%28TRD_DT%20AS%20TIMESTAMP%29%60%2C%20mark%20it%20as%20temporal%2C%20and%20use%20that%20column%20in%20your%20Box%20Plot.%20This%20ensures%20the%20date%20is%20recognized%20and%20formatted%20correctly%20by%20the%20chart%20plugin.%20This%20approach%20is%20consistent%20with%20maintainers%27%20guidance%20for%20similar%20temporal%20data%20issues%20in%20Superset%20%28%5Breference%5D%28https%3A//github.com/apache/superset/issues/27798%29%29.%0A%0ALet%20me%20know%20if%20you%20want%20more%20details%20on%20the%20technical%20differences%20in%20how%20Box%20Plot%20and%20other%20charts%20handle%20temporal%20fields.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37608) -- 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]
