[GitHub] [superset] villebro commented on issue #17154: Druid SQL dataset __time column registered as a LONG rather than TIMESTAMP

[GitBox <gi...@apache.org>]

villebro commented on issue #17154:
URL: https://github.com/apache/superset/issues/17154#issuecomment-948008974


   @john-bodley I haven't worked on this stuff for a while, so I may be rusty on the details. But when adding a new dataset, I believe we're using the SQLAlchemy inspector method `get_columns(table, schema)`. And when fetching metadata for a SQL query, we're using the cursor description, which almost always differs from the table metadata returned by `get_columns`, even for a `SELECT * FROM table`. I'm betting `pydruid` is returning `LONG` for `__time` on `inspector.get_columns`, but `TIMESTAMP` on `cursor.description`. Which is weird, as I would have expected it to be the other way around, i.e. more accurate metadata on `inspector.get_columns` than `cursor.description` on a similar query.


-- 
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: notifications-unsubscribe@superset.apache.org

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