The fix is ready, it'll be part of the next release.

In the meantime, you can work around the problem by setting an analyzer or normalizer on your field using @KeywordField(normalizer = ...) or @FullTextField(analyzer = ...). Which is something you'll want to do anyway to take advantage of full-text capabilities.

See here for more information about analysis, here for more information about property/field mapping. In particular, here is how to define your analyzers/normalizers with the Lucene backend.