The whole thing seems a bit weird. The relevant code is only executed when a field we project on has a bridge that doesn't implement TwoWayFieldBridge.

But if a field has a bridge that does not implement TwoWayFieldBridge, why in the world would we allow users to project on this field? I mean, the purpose of TwoWayFieldBridge is to allow such projections... For Lucene queries, the implementation seems to fail whenever the field bridge doesn't implement TwoWayFieldBridge: org.hibernate.search.engine.impl.DocumentBuilderHelper.populateResult(String, FieldBridge, Store, Object[], Document, ConversionContext, int)

I'm refactoring the code for a different ticket ( HSEARCH-2360 In Progress ), and for now I kept the code, but I wonder if I shouldn't just drop it...