JARVIS-DFT Optimade API returns wrong data when using paranthesis

[mehmetgiritli]

Hi,

Using parenthesis around an Optimade filter in the query returns wrong results, and returns almost like the entire database.

Here is an example with a very simple Optimade filter: elements HAS ALL "H"

Produces irrelevant results with 979637 items:
https://jarvis.nist.gov/optimade/jarvisdft/v1/structures/?filter=(elements+HAS+ALL+%22H%22)

Produces correct results with 21 items:
https://jarvis.nist.gov/optimade/jarvisdft/v1/structures/?filter=elements+HAS+ALL+%22H%22

Thanks

[ml-evs]

Bumping this, it also seems to respond incorrecly to many other queries, e.g.,

https://jarvis.nist.gov/optimade/jarvisdft/v1/structures/?filter=immutable_id="123"

returns the whole database

The majority of custom properties found on strucutres are also not reported at /info/structures (along with many mandatory OPTIMADE properties).

[knc6]

Thanks for the bump @ml-evs , to @mehmetgiritli for the wait.

I no longer have direct deploy access to jarvis.nist.gov, but I'll ask the management folks there.

I did hit the same bug on our own endpoint, so thanks for the prompt.

Fixed at https://atomgpt.org/optimade/v1/structures?filter=immutable_id="123" by parsing with optimade-python-tools' Lark grammar.