escape lucene key words so that it can parse the string

Description

From bug hunt, server logs the error:

When this happen we should try to gather more information like document, project, iteration ids via lucene projections, and compare them to the values in the entity.

Environment

None

Activity

Show:
Sean Flanigan
July 14, 2016, 5:31 AM

Better still, we should find a way of escaping strings (ie keywords and special characters) so that Lucene will be able to parse the query.

Patrick Huang
July 15, 2016, 4:08 AM

There is no other information available when this happens. Only the text itself. If we want we could pass those information from the GWT client but given that we will be focusing more on the new editor I will not make the change.

Sean Flanigan
July 15, 2016, 4:26 AM

There is no other information available when this happens. Only the text itself. If we want we could pass those information from the GWT client but given that we will be focusing more on the new editor I will not make the change.

That's our excuse for so many things, and yet the new editor is still not ready!

Anyway, fair enough, but please add a prominent comment to the relevant GWT service, so that, when we port that code to a REST service for the new editor, we can be sure to add the extra context info there. (In fact, when searching based on TextFlow content, we shouldn't even pass the (potentially bulky) text itself, because the server can get it if we just pass the textflow id.)

Ready for Release

Assignee

Patrick Huang

Reporter

Patrick Huang

Labels

None

Tested Version/s

None

Time tracking

0m

Time remaining

1h 30m

Sprint

None

Fix versions

Priority

Low
Configure