lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Costermans (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4009) Implement toString() method in TermsFilter
Date Sun, 22 Apr 2012 09:51:35 GMT


Tim Costermans commented on LUCENE-4009:

Hey Chris,

Basically all the subclasses of should implement their own
toString() method.
Maybe this can be enforced by adding this to the Filter class.
public abstract String  toString();
I was going to investigate this, but this will be something for next week.
> Implement toString() method in TermsFilter
> ------------------------------------------
>                 Key: LUCENE-4009
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/other
>    Affects Versions: 3.5, 3.6
>            Reporter: Tim Costermans
>            Priority: Trivial
>         Attachments: LUCENE-4009__Improved_previous_implementation_of__toString()_method_in_TermsFilter_+_added.patch,
> LUCENE-1049 introduced a enhanced implementation of the toString() method in the BooleanFilter
> This was an improvement, however I'm still seeing a lot Lucene filter classes not overriding
the toString method resulting in a toString returning the classname and the hashcode of the
> This can be useful sometimes, but it's totally not useful in my case.
> I want to see the properties set in the filters so I know which Lucene query was created.
> Now:
> BooleanFilter(+BooleanFilter(BooleanFilter( BooleanFilter(
> Wanted behavior:
> BooleanFilter(+BooleanFilter(BooleanFilter(+inStock:Y +barCode:12345678) BooleanFilter(+isHeavy:N

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message