[ 
https://issues.apache.org/jira/browse/LUCENE-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793205#comment-13793205
 ] 

ASF subversion and git services commented on LUCENE-5278:
---------------------------------------------------------

Commit 1531479 from [~rcmuir] in branch 'dev/trunk'
[ https://svn.apache.org/r1531479 ]

LUCENE-5278: remove CharTokenizer brain-damage from MockTokenizer so it works 
better with custom regular expressions

> 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
>            Assignee: Robert Muir
>            Priority: Trivial
>         Attachments: LUCENE-5278.patch, LUCENE-5278.patch, 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to