-
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
Type filter in Dataset CRUD view doesn't work #11266
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
@etr2460 I'm not being able to reproduce this. The filter applies to |
I'm also unable to reproduce. @etr2460 are some of these datasets using the native druid connector? It's possible the logic that determines the datasets type is incorrectly implemented for druid datasources. As @dpgaspar mentioned the actual filtering logic is applied to the |
@etr2460 is the issue here that physical datasets are incorrectly labelled as virtual, or that the filter logic is not accounting for other instances/types of virtual datasets? |
I think it's the latter. The datasets seem to be correctly labeled as Virtual, but they still show up when you filter to Physical only datasets |
ok, I see what the discrepancy is here. The label of "Physical" and "Virtual" is based on the presence of the So the question is, which attribute determines if it's a "virtual" dataset? The presence of the |
hmmm, looks like |
When I select "Physical" as the dataset type I still get virtual datasets
Expected results
Only get physical dataset types
Actual results
Also get virtual datasets
Screenshots
The text was updated successfully, but these errors were encountered: