Task #12436 (new)
Opened 10 years ago
Last modified 10 years ago
BUG: Search for AND and OR — at Version 1
| Reported by: | pwalczysko | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 5.0.3 |
| Component: | Client | Version: | 5.0.2 |
| Keywords: | n.a. | Cc: | ux@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by pwalczysko)
A query like
nd2 weird AND attachment
will be interpreted atm by our clients as
weird AND attachment
This is because Lucene is interpreting the query as such
(nd2 SHOULD, weird MUST, attachment MUST)
which marginalises the SHOULD term. The expected result with
nd2 SHOULD, (weird MUST attachment MUST) SHOULD
interpretation is passed to Lucene using syntax
nd2 OR (weird AND attachment)
This is not possible now in the clients, because the clients strip the brackets away (probably).
dlindner suggests the solution:
for a query like
nd2 weird AND attachment
the clients will add the brackets for Lucence and pass
nd2 (weird AND attachment)
which would result in the expected result for the user.
