In examples of Analizers that I saw, filters change search results for index of one specific fields. I haven't seen filter that do following: check whether field matches some conditions and if not, extracts the whole object found from search result. I have such task: search should return only objects that current user is authorized to see. I can do it with loop on search results before I return it, but it will be more natural if it just will not returned from search. Can somebody explain to me if it is possible and if true, how to do it.

Hi,

I think your are mixing up two orthogonal concepts here - projections and filtering. Projection is the idea of skipping the round trip to the database and return data directly from the Lucene index. The advantage being speed, the disadvantage being that you are working with object arrays instead of managed objects.
The concept of filtering comes from the Lucene world and allows to "narrow down" the results of a raw search by applying a chain of filters. Since this is a Lucene feature you have to filter on Field values, but that does not mean that you cannot have Hibernate managed entities as result of your search. If you want to implement a security filter just index the property you need for authorization and filter on it.
Btw, Analyzers are yet another concept.
I recommend you look up these three concepts in the Hibernate Search Online documentation. I think it even has an example for a security filter.

--Hardy

Thanks. I thought that filters defined only as part of analizer, but I see that I was wrong. Now, I understand that I need filter, but it creates other question. The example of security filter in documentation checks in index whether level==5. It means that there is field indexed with "level" in every object that can be result of query the filter applied to. Imagine, I have classes A and B, the filter should be applied to and base class C, these objects inherite from. Class C has "level" field. Will the filter work, or it will complain that query results don't contain "level" field?

Provided level is annotated with @Field it should work. Base class properties can be indexed as well. Just annotate them accordingly.

--Hardy