"cannot read property of undefined" and "shards failed"

[goochjs (Jeremy Gooch)]

Hi,

We've started seeing some errors when searching Kibana. I think the cases are related to where the team have been looking for middleware message IDs, which contain colons. Is this the cause?

We're running v6.4.2.

Thanks,

J.

[thomasneirynck]

can they quote the values of the search query?

in the lucene query syntax, the colon is used to separate the field-name from the query-string value.

something like: ID:"277032:12341:14431..."

[goochjs (Jeremy Gooch)]

Thanks - that's the advice I've given, on the assumption (which you've confirmed) that colon is a reserved character. I logged it here because the error messages are unexpectedly severe and there was concern that something else was awry.