-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[db_specific] CockroachDB does not support to_timestamp #15825
Comments
Hi @korpa , we may not get to any db specific issues soon enough, feel free to open a PR, we are happy to review! |
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 |
This issue still exists. Please do not close |
It seems that someone implemented this feature in CockroachDB cockroachdb/cockroach#82523 Hopefully this will released in a minor version that we do not have to wait another 6 months for the next big release of CockroachDB |
Currently, I face this error when using Specifically, it says CockroachDB doesn't have that exact https://www.cockroachlabs.com/docs/stable/functions-and-operators.html#date-and-time-functions is this a sqlalchemy driver issue or superset? driver: https://github.com/cockroachdb/sqlalchemy-cockroachdb |
Any advice for this issue? - running into this as well and am happy to dig in if there is some rough guidance on where the root issue may exist. The workaround I am doing is roughly as follows
This prevents the query generator from adding the to_timestamp when filtering with a time range. |
@yousoph @junlincc - seems like this is a matter of updating the db spec for crdb here https://github.com/apache/superset/blob/master/superset/db_engine_specs/cockroachdb.py I am going to play around with getting a local superset env set up and will see if I can validate that is the correct spot to implement how to handle time filters. |
I have a fix for this running locally and in a prod env using version 2.1.0. The PR that should address this is #24711 |
A clear and concise description of what the bug is.
Expected results
Graph should appear
Actual results
Error is shown:
Screenshots
Without timefilter:
With timefilter:
How to reproduce the bug
Create a graph on database "CockroachDB" and add a time filter
Environment
(please complete the following information):
node -v
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
In Superset 1.0 CockroachDB works fine with time filters. After upgrading to 1.2 this issue appears
The text was updated successfully, but these errors were encountered: