-
Notifications
You must be signed in to change notification settings - Fork 0
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
Errors while using filters #136
Comments
I think a lot of this is coming down to differences in the database implementation - I had to do the date cast in a slightly different way than it works in postgres, but I have something that is working locally. Can you provide specific URLs for the other broken filters? |
@vlad-ignatov pinging on this from the meeting - dates are fixed, just get me urls for other broken filters. |
I don't see the dates being fixed. There are too many errors and this is hard to test. Let me lis a few errors, and I'll test again after you fix them. Using
|
@vlad-ignatov ok - looks like this is I know you've got them split out in some way at the dashboard layer - do you want |
addressed via #139 |
Not sure what the exact error is since I only see the generic error messages. Example:
https://api.smartcumulus.org/data-packages/data_metrics__count_c_system_use_observation_code__001/chart?column=year&filter=year%3AafterYear%3A2000-01-01
It looks like you are expecting just the year number here. The question is, for compatibility reasons, can you accept
YYYY-MM-DD
and extract the info from it? (applies to all date filters)Other filters that do not seem to work correctly:
<
and<=
(eg.:cnt < 10000
)The filter implementation can be very tricky. Keep in mind that at the database level, all columns other than cnt, regardless of their data type are stored as text (to allow cumulus__none and other custom values). Then string operators and filters are also applicable to non-string columns. As a reference, here is the relevant part of the dashboard's current filter implementation:
The text was updated successfully, but these errors were encountered: