Perhaps a minor thing, but lucene regex doesn't appear to support \n natively. Instead the \n needs to be provided at the json level. Currently we pass the \n through all the way to lucene and don't find anything. Should be an easy fix, but we might want to consider if there are other special characters beyond \n (\r, \t? others? i dunno...) that we want to handle
• Aqwww23 renamed this task from insource: queries can't search for the return character to rikvip.May 13 2016, 9:34 PM
• Aqwww23 triaged this task as High priority.
• Aqwww23 set the point value for this task to 12.Comment Actions
Krenair renamed this task from rikvip to insource: queries can't search for the return character.May 13 2016, 9:53 PM
Krenair raised the priority of this task from High to Needs Triage.
Krenair removed the point value for this task.