Time Grain Not Available in Azure Databricks

[rbk-paul]

A clear and concise description of what the bug is.

The "Time Grain" filter does not have any options available (shows "0 Options"), despite detecting correct the various "Time Columns". This problem exists for all Visualization Types.

Found a similar issue reported but was closed and marked stale: https://github.com/apache/incubator-superset/issues/8009

Data Source is from Azure Databricks.

Expected results

Time Grain filter shows different options like Year, Month, Day...

Actual results

Shows "0 Options"

Screenshots

How to reproduce the bug

1. Create any Visualization Type connecting to any tables from a Azure Databricks data source
2. "Time Grain" does not show options

Environment

(please complete the following information):

• superset version: 0.36.0
• python version: 3.7.7
• node.js version: v13.11.0
• npm version: 6.13.7

Checklist

Make sure these boxes are checked 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.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.73. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[MApeldoorn]

Hi,

I am having the same issue. Running SuperSet 0.36, but had the same problem in 0.29.

Connection to a sqlalchemy_sqlany backend. DATETIME_ID (type TIMESTAMP) and DAET_ID (type DATE) are giving 0 Time Grain option(s). I have tried multiple datetime-translation, but no success.

With kind regards, Mark

[mistercrunch]

What does your connection string look like? What SQL dialect is this most like? Hive?

You probably want to add a new module here: https://github.com/apache/incubator-superset/tree/master/superset/db_engine_specs

[villebro]

@rbk-paul are you connecting using this connector? https://pypi.org/project/databricks-dbapi/

[rbk-paul]

@villebro. yes, using the connector you specified.

@mistercrunch, connection string looks like this: databricks+pyhive://token:databrick_access_token>@<databrick_host:/

[MApeldoorn]

@mistercrunch : In my case: sqlalchemy_sqlany://..., connecting to Sybase

[MApeldoorn]

What does your connection string look like? What SQL dialect is this most like? Hive? You probably want to add a new module here: https://github.com/apache/incubator-superset/tree/master/superset/db_engine_specs

It worked for me. I copied the mssql.py db_engine_specs, renamed it to sqlalchemy_sqlany. Only thing I had to fix after that was replace the "0" within DATEADD and DATEDIFF. The results these functions get comparing to todays datetime is giving an error (probably too high value). Replacing "0" by e.g. '2020-01-01' did the trick.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.