dosubot[bot] commented on issue #41452: URL: https://github.com/apache/superset/issues/41452#issuecomment-4808753084
<!-- Answer --> Your suspicion about PR #38017 is likely correct. That PR introduced **time grain-aware formatting** for ECharts X-axes that normalizes timestamps to time boundaries and explicitly removes milliseconds via `setMilliseconds(0)` [[1]](https://github.com/apache/superset/pull/38017). This directly impacts epoch_ms timestamp handling. The normalization logic snaps dates to boundaries (midnight UTC for days, top of hour for smaller intervals, etc.), which can break rendering when PinotDB epoch_ms timestamps are used—especially if no explicit time grain is configured or the grain doesn't match the data's actual granularity. Several follow-up PRs were merged after #38017 to address edge cases it introduced: - **Phantom label suppression** — fixed spurious labels like ".345ms" appearing at axis edges when Time Grain is None [[2]](https://github.com/apache/superset/pull/39972) - **X-axis label deduplication** — addressed consecutive identical labels with coarse time grains [[3]](https://github.com/apache/superset/pull/38733) - **Temporal X-axis regression guards** — added tests to prevent NaN/incorrect labels for epoch values [[4]](https://github.com/apache/superset/pull/39208) **Possible workarounds to try:** 1. Set an explicit time grain (e.g., `P1D`, `PT1H`) that matches your data granularity 2. Use a custom date format instead of "Adaptive Formatting" in the X-axis configuration The relevant code is in `superset-frontend/plugins/plugin-chart-echarts/src/utils/formatters.ts` and `src/Timeseries/transformProps.ts` [[1]](https://github.com/apache/superset/pull/38017). If the follow-up fixes (already merged) haven't resolved this for PinotDB epoch_ms specifically, it may need an additional patch to handle the case where timestamps arrive as raw epoch milliseconds without an associated time grain. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).* --- Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=40fa9316-706b-4637-b5b8-e92cb9967c1e) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset) -- 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]
