You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2020/12/14 13:10:32 UTC
[GitHub] [incubator-superset] 0xBADBAC0N opened a new issue #12037: Custom datetype for Dataset is not passed to group by operation
0xBADBAC0N opened a new issue #12037:
URL: https://github.com/apache/incubator-superset/issues/12037
A clear and concise description of what the bug is.
### Expected results
If I use a custom temporal column (eG string type but contains %Y%m%d) the type is correctly set in the conditions (where clause) but should also be set correctly in all other locations (eG group by)
### Actual results
what actually happens:
I have set the correct settings for the dataset:
and the changes where applied correct to the where clause, but not the group by clause.
This generated query would also not really work as in Hive select UNIX_TIMESTAMP('2012-05-10'); (=> NULL)
would break as the custom schema is not pushed down. With pushing down a proper schema, it would work like select UNIX_TIMESTAMP('2012-05-10', 'yyyy-MM-dd'); (=> 1336608000)
#### How to reproduce the bug
1. Create a temporal column as string and add the formatting manually.
2. Try to group by that column in Hive.
3. Click on View Query and see the raw query.
4. See error
### Environment
(please complete the following information):
- superset version: 0.38
- python version: python 3
- node.js version: n/a
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [X] I have reproduced the issue with at least the latest released version of superset.
- [X] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
Add any other context about the problem here.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org