New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postings highlighter does not support wildcards #4042
Comments
Thanks for reporting this, we'll see what we can do about it. |
I read it as if it does not account for any boolean logic and phrases given the emphasis on that in the doc and missed wildcard aspect till i hit the issue. Hopefully trailing wildcards/prefixes will be easy :-) |
Hi Luca, Are trailing wildcard supposed to work? I built 0.9.7-SNAPSHOT as of an hour ago and it does not seem to work. Actually even regular terms seem to not highlight randomly I can't quite pin when it highlight and when not. Something seems to be broken? Alex |
This is in the just released 0.90.6, no need to build from a snapshot. Just tested with 0.90.6 and saw trailing wildcard matches highlighted, as well as ordinary queries (e.g. match query). |
Luka, Let me test 0.9.6 (it was not in maven couple oh hours ago yet) and if it thanks, On Mon, Nov 4, 2013 at 12:11 PM, Luca Cavanna notifications@github.comwrote:
|
Luka, It does not work with 0.90.6 either. Just a very simple example (not exactly my problem of not highlighting at all but highlighting incorrectly):
|
Yeah, I'm seeing weird stuff happening here too, eg:
It's like the offsets are set on the first document, then not reset for subsequent documents. |
Indeed, this is odd. I'm looking into it and I'll open another issue later on as the problem is not only with wildcards. |
Currently postings highlighter does not support wildcards and I suspect prefix queries as well - it would only highlight complete terms.
Would it be possible to make it support at least trailing wildcards and prefix queries such as photo*
if not possible, the documentation should state that
The text was updated successfully, but these errors were encountered: