-
Notifications
You must be signed in to change notification settings - Fork 39
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
Querying on last_modified not working. #1076
Comments
Yep, something is broken here. You can try flipping the comparison at the link below and you'll see the same IDs turning up. We definitely have a test for this: optimade-python-tools/tests/filtertransformers/test_mongo.py Lines 522 to 568 in bb3c5a1
Looks fine to me, so I guess the issue is either in the parsing (i.e. does it get to the timestamp detection stage) or in Mongo itself (i.e. the query we are generating above does not do what we think it does). We should probably check if it works for elastic too. |
I think I made a typo in the link I wrote "filer" instead of "filter". |
Haha phew, I had tried to replicate this in the past and struggled. I must have made the same typo a few times myself 😅 |
I have noticed that querying on the
last_modified
field is not very reliable.I performed the query localhost:5000/v1/structures?filer=last_modified>=2019-07-09T05:14:38Z
The result contains the entry "mpf_1" which has last_modified = 2019-06-08T03:13:37Z which is clearly outside the requested data range.
I used optimade python tools version 0.16.10
The text was updated successfully, but these errors were encountered: