lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3064) add checks to MockTokenizer to enforce proper consumption
Date Thu, 12 May 2011 13:35:47 GMT

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

Robert Muir commented on LUCENE-3064:
-------------------------------------

Committed revision 1102290.

I know the checks aren't totally perfect, but I think this is an important step to switching
all of our APIs over to reusableTokenStream (LUCENE-3040), and ultimately looking at a way
to do something like deprecate tokenStream.

For this reason I will now look at backporting to 3.x

> add checks to MockTokenizer to enforce proper consumption
> ---------------------------------------------------------
>
>                 Key: LUCENE-3064
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3064
>             Project: Lucene - Java
>          Issue Type: Test
>            Reporter: Robert Muir
>             Fix For: 3.2, 4.0
>
>         Attachments: LUCENE-3064.patch, LUCENE-3064.patch, LUCENE-3064.patch, LUCENE-3064.patch
>
>
> we can enforce things like consumer properly iterates through tokenstream lifeycle
> via MockTokenizer. this could catch bugs in consumers that don't call reset(), etc.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message