You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nik Everett (JIRA)" <ji...@apache.org> on 2013/10/11 21:33:41 UTC
[jira] [Updated] (LUCENE-5278) MockTokenizer throws away the
character right after a token even if it is a valid start to a new token
[ https://issues.apache.org/jira/browse/LUCENE-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nik Everett updated LUCENE-5278:
--------------------------------
Attachment: LUCENE-5278.patch
This patch "fixes" the behaviour from my perspective but breaks a bunch of other tests.
> MockTokenizer throws away the character right after a token even if it is a valid start to a new token
> ------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-5278
> URL: https://issues.apache.org/jira/browse/LUCENE-5278
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Nik Everett
> Priority: Trivial
> Attachments: LUCENE-5278.patch
>
>
> MockTokenizer throws away the character right after a token even if it is a valid start to a new token. You won't see this unless you build a tokenizer that can recognize every character like with new RegExp(".") or RegExp("...").
> Changing this behaviour seems to break a number of tests.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org