Skip to content
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

Filter for datetime value returns "Cannot compile Column object until its 'name' is assigned." #22574

Closed
1 of 3 tasks
stephanclaus opened this issue Jan 3, 2023 · 6 comments
Closed
1 of 3 tasks
Assignees
Labels
#bug Bug report

Comments

@stephanclaus
Copy link

A clear and concise description of what the bug is.

How to reproduce the bug

  1. Build a chart on a data set that contains a datetime column
  2. Add this chart to a dashboard
  3. add a dashboard filter on the datetime column
  4. apply the filter
  5. See error

Expected results

the chart is filtered by the value

Actual results

An error is raised:

Cannot compile Column object until its 'name' is assigned.

This may be triggered by:
Issue 1011 - Superset encountered an unexpected error.

Screenshots

Screenshot 2023-01-03 at 21 32 45

Environment

(please complete the following information):

  • Chrome Version 108.0.5359.124 (Official Build) (x86_64)
  • superset version: 2.0.0
  • connecting to snowflake database

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Superset 2.0.0 and snowflake/sqlalchemy seems to have more problems with date time handling. The same approach is working fine if the filter column is a date field.

@stephanclaus stephanclaus added the #bug Bug report label Jan 3, 2023
@michael-s-molina
Copy link
Member

@geido @kgabryje This may be related to the bug we were investigating with drill to detail and Snowflake.

@zhaoyongjie
Copy link
Member

zhaoyongjie commented Jan 26, 2023

Hi @stephanclaus, I can't reproduce this issue when I use orders table of the TPCH in the Snowflakes. Could you add more details for our reproduce it?

Test environment:

  • Latest master branch
  • orders table of TPCH
  • Snowflakes
  • Add time range filter in the Native filter
  • Right-click on the Chart to select a column to drill detail

image

@stephanclaus
Copy link
Author

Hi, so the column you are using the the order_date column? Is this a datetime data type actually?

@zhaoyongjie
Copy link
Member

yes, it does. o_orderdate is a DateTime column in standard TPCH.

@stephanclaus
Copy link
Author

okay, so it is in the standard TPCH, but not in Snowflake:
Screenshot 2023-01-26 at 18 45 26
Screenshot 2023-01-26 at 18 42 12

So I think your test case is invalid.

@villebro
Copy link
Member

Closed by #22872

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

4 participants