Search is still not implemented correctly

Steps to reproduce

The search facilities of Opencast 2.x are one of the most important product features. While the product has the potential to offer a great search facility, it's current implementation is both incorrect and suboptimal.
This task is about improving the quality of Opencast 2.2 by making its powerful search facilities finally work correctly.

Originally, in Opencast 2.0, there were many problems regarding the search facilities (example: Search on Events table).
While most people likely have not realised, the Admin UI sent the search string to the backend where a search string parser (with support for different special characters as - for exclusion, + for inclusion, and/or, etc.) often caused exceptions which again caused the search results to be simply wrong.

In Opencast 2.1.0, a patch for this was applied, see https://opencast.jira.com/browse/MH-11182?jql=text%20~%20search%20ORDER%20BY%20created%20DESC. This patch does escape those "special characters" so that the search query parser does not cause exceptions anymore.
While this is an improvement, it comes with the following two problems:

  • Support for advanced search queries removed (no more +, -, etc)

  • Still not handling hyphens correctly

Steps to reproduce:
1. Create an Event with the title abc-def-ghi
2. Search for abc-def-j3iojflijsdfli

Actual Results:
The search string matches to the event tile 'abc-def-ghi' although this is wrong.

Expected Results:
This was just an example.

Workaround (if any):

Activity

Show:
Sven Stauber
June 3, 2016, 8:44 AM

At least partially solved by

Duplicate

Assignee

Sven Stauber

Reporter

Sven Stauber

Severity

Incorrectly Functioning With Workaround