Details

Description

LUCENE-1049 introduced a enhanced implementation of the toString() method in the BooleanFilter clause.
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 object.
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.

Tim Costermans
added a comment - 22/Apr/12 10:49 Hey Chris,
Basically all the subclasses of org.apache.lucene.search.Filter should implement their own toString() method.
Maybe this can be enforced by adding this to the Filter class.
@Override
public abstract String toString();
I was going to investigate this, but this will be something for next week.