Fixed
Details
Assignee
Yoann RodièreYoann RodièreReporter
Sanne GrinoveroSanne GrinoveroComponents
Sprint
NoneFix versions
Priority
Critical
Details
Details
Assignee
Yoann Rodière
Yoann RodièreReporter
Sanne Grinovero
Sanne GrinoveroComponents
Sprint
None
Fix versions
Priority
Created September 10, 2013 at 3:05 PM
Updated December 13, 2019 at 2:57 PM
Resolved December 6, 2019 at 1:24 PM
Several other libraries are embedding Hibernate Search to bridge custom values into Lucene indexes but so far we're expecting a 1:1 match between class definitions and different indexed "types".
Some indexed "types" should be representable by the same valueholder java type but having attributes defined at bootstrap (for example from a protobuf schema).
A common requirement is to have the "user type" defined by a name rather than a class; that implies then that we need to be able to have queries targeting (narrowing down) to this specific type based on the string name rather than the Java class definition.