dosubot[bot] commented on issue #30361:
URL: https://github.com/apache/superset/issues/30361#issuecomment-2368296713

   <!-- Greeting -->
   Hey @DLoc-poste! I'm Dosu, a bot here to help you with bug fixes and answer 
your questions. Let's work together to tackle this issue!
   
   <!-- Answer -->
   The issue you're encountering with date fields displaying as "NaN" in Apache 
Superset 4.0.2 dashboards is likely due to inconsistencies in how timestamps 
without explicit timezones are handled. Apache Superset relies on Pandas to 
read SQL into a DataFrame, and Pandas may ignore the DB-API type code, leading 
to issues with timestamp serialization. This can result in timestamps being 
incorrectly coerced, causing them to display as "NaN" in the client.
   
   To resolve this, ensure that both the PostgreSQL database and the Apache 
Superset backend are configured to use the same timezone, preferably UTC, to 
avoid incorrect coercion of temporal fields 
<sup>[[1]](https://github.com/apache/superset/blob/master/docs/docs/configuration/timezones.mdx)</sup>.
   
   Additionally, I found a similar closed issue related to "NaN" in legend 
dimensions, which might provide some context: [NaN in legend 
dimension](https://github.com/apache/superset/issues/16655) 
<sup>[[2]](https://github.com/apache/superset/issues/16655)</sup>.
   
   The pull request you mentioned 
([#24696](https://github.com/apache/superset/pull/24696)) does not have 
specific details available in the repository, so it might not directly address 
your issue 
<sup>[[1]](https://github.com/apache/superset/blob/master/docs/docs/configuration/timezones.mdx)</sup>.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


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