dosubot[bot] commented on issue #31192: URL: https://github.com/apache/superset/issues/31192#issuecomment-2506705147
<!-- Greeting --> Hey @yuribogomolov! I'm here to help you with any bugs, questions, or contributions you have for Superset. Let's tackle this issue together! <!-- Answer --> A similar issue was discussed in a closed thread regarding Apache Pinot and Superset, where the problem was related to aliasing in SQL queries. The solution involved updating the `pinotdb` SQLAlchemy driver to the latest version and using a calculated column in Superset to cast the temporal field to a timestamp. This approach includes creating a derived column in Pinot as a `timestamp` type instead of `long`, removing the `epoch_ms` tag in the column config, syncing column metadata in the Dataset Model in Superset, and using the new derived column in the chart <sup>[[1]](https://github.com/apache/superset/issues/26303)</sup><sup>[[2]](https://github.com/apache/superset/issues/25749)</sup>. Additionally, Superset handles conflicts between original column names and aliases by updating the alias to avoid conflicts. If a `SELECT` clause alias is named the same as a source column, Superset changes the alias name by appending `__` to it if it appears in the `ORDER BY` clause <sup>[[3]](https://github.com/apache/superset/blob/master/superset/models/helpers.py)</sup>. This might be relevant to your issue with aliasing in the query. <!-- 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]
