-
Notifications
You must be signed in to change notification settings - Fork 5
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
q=
query with or
does not work as expected
#520
Comments
or
does not work as expectedq=
query with or
does not work as expected
@tloubrieu-jpl do you still have this environment set up? I was hoping you might be able to test with an up-to-date version of registry-api before I dive into trying to replicate - the following initial tests against the I&T database init indicate that With two bundles, four collections:
|
Confirmed working as-expected on production API, too: 534 Bundle |
Running original query against prod registry/API A - A or B returns 2822398 So behaviour is as-expected |
Closing as not-a-bug after confirming with @tloubrieu-jpl |
Checked for duplicates
No - I haven't checked
🐛 Describe the bug
I tried to query my local pds registry with:
And expected to see all labels with Moon target name or MOON spheroid name. However, I instead got no data at all. Each of these alone produced what I expected, ~1000 for target name and ~285 for spheroid name.
After adding the target name tags to the lola xml, I got back only the lola xml. So it seems like or is functioning as and.
🕵️ Expected behavior
I expected to get back around 1283 responses.
📜 To Reproduce
Create treks and lola pds4 xml from the commands in the registry. Lola command is not merged, but on branch stac_utility
load the xml files into the registry
go to or curl
http://localhost:8080/products?q=((pds:Target_Identification.pds:name eq "Moon") or (cart:Geodetic_Model.cart:spheroid_name eq "MOON"))&limit=10000
🖥 Environment Info
Version of this software stac_utility branch of registry
Operating System: Intel Macbook
🦄 Related requirements
TBD
The text was updated successfully, but these errors were encountered: