Very probably affects 5.6 and even 5.5, but I didn't check.
The container bridges are wrapped around element bridges in the BridgeFactory, before {{NullEncodingTwoWayFieldBridge}} and such could have been wrapped around element bridges.
As a result, null values are handled by element bridges themselves, and not by null codecs like everywhere else.
This can result in inconsistent behavior. For instance {{org.hibernate.search.bridge.builtin.NumericFieldBridge.set(String, Object, Document, LuceneOptions)}} indexes null values as strings (which is the behavior in container bridges), whereas {{org.hibernate.search.bridge.builtin.NumericFieldBridge.INT_FIELD_BRIDGE. \ {... \ }.createNullMarker(String)}} instructs Hibernate Search to index null values as numeric values (which behavior the behavior outside container bridges). |
|
