Change Details

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

Perhaps a minor thing, but lucene regex doesn't appear to support \n natively. Instead cirrus needs to parse \n into a literal return charater which will then be re-encoded to \n at the json level when making requests to elasticsearch. 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

Perhaps a minor thing, but lucene regex doesn't appear to support \n natively. Instead the \n needs to be provided at the json levelcirrus needs to parse \n into a literal return charater which will then be re-encoded to \n at the json level when making requests to elasticsearch. 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