Hi,

As I understand, the filtered types array that is the parameter or FullTextEntityManager.createFullTextQuery() has use only when projection is not used, am I right? If that is the case, I suggest removing the filtered type parameter from the documentation examples 5.9 and 5.10. Otherwise I would like to understand how I'm wrong.

Thanks,

Gabriel

Hi Gabriel,
no filtered types should work fine even with projections. I assume you've tried it and have an issue with it? Can you show a non working example?

I don't experience any problems when not using filter type with projections, I just wanted to make sure I'm not missing anything and that there is no performance loss for this case.

From my understanding, the filter type is used only for the Hibernate query that is executed after the Lucene query, and when projections are used there is no subsequent Hibernate query, so in these cases the defined filter types don't matter, is that correct?

Thanks.

no actually the filter types have nothing to do with the hibernate query eventually performed afterwards when not using projections.

It's being used to restrict which Lucene Documents are eligible to match your query; you might not notice it being applied as some properties you're requiring in your query might be only matched by specific types, but it might still be useful in case of inheritance.

In case you have multiple entities in multiple indexes, restricting the type is performance wise more efficient, as it will perform the query only the needed indexes, instead of searching all indexes for potential matches.

Thanks for the explanation. So I will keep the filtered type.