lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Commented: (LUCENE-1636) TokenFilters with a null value in the constructor fail
Date Mon, 05 Oct 2009 21:25:31 GMT


Uwe Schindler commented on LUCENE-1636:

This change is also noted in the backwards compatibility section of Lucene 2.9.

The assignment of filter in the ctor is totally useless, as the super ctor does it already,
so it the problem of this third party software that used the API in an undocumented way. I
am sorry for your problems, but the author of lucene-ja should provide a fix, if you have
the source code available, it is a less important problem, if it is closed source, you have
to ask the author to fix it soon.

> TokenFilters with a null value in the constructor fail
> ------------------------------------------------------
>                 Key: LUCENE-1636
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 2.9
>            Reporter: Wouter Heijke
>            Assignee: Michael McCandless
>             Fix For: 2.9
>         Attachments: LUCENE-1636.patch
> While migrating from 2.4.x to 2.9-dev I found a lot of failing unittests.
> One problem is with TokenFilters that do a super(null) in the constructor.
> I fixed it by changing the constructor to super(new EmptyTokenStream())
> This will cause problems and frustration to others while migrating to 2.9.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message