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
Lucene Query Builder Unification #2802
Conversation
Rather than have 2 implementations of the query parsing logic, omero.gateway now uses the byLuceneQueryBuilder method to have the custom query built server-side.
Now the date query of byLuceneQueryBuilder can be based on either the import date or the acquisitionDate by setting the new parameter.
SearchControl was not properly making use of the HqlControl _configure method. With this commit, all of the options from HqlControl are also provided for regular search, including output style and `--all` for querying across groups.
Some searches like '%' generated empty strings in LQB which led to invalid query exceptions "<EOF>" etc.
Conflicting PR. Removed from build OME-5.0-merge-push#110. See the console output for more details. |
This all seems to be behaving as expected.
None of these are blockers (or even related to this PR?) so: good to merge. |
Thanks, @will-moore. |
Lucene Query Builder Unification
@will-moore Sounds reasonable; I'm going to make your proposed changes for Insight in another PR. |
--rebased-to #2858 |
With the migration of @dominikl's
byLuceneQueryBuilder()
method to the server in gh-2676 all other clients (OMERO.web and the CLI) need to be updated to make use of the single implementation. Testing involves showing that results from any one of the clients match the other 2 clients. Search options which should be involved include:Testing user/group semantics via the CLI might be considered out-of-scope.
Follow-ons to this PR will include:
modify server-side implementation to better handle some queriesadded here with aa21d07Note: This PR replaces gh-2784