]
Hardy Ferentschik resolved HSEARCH-664.
---------------------------------------
Resolution: Rejected
It is probably not a good idea to let the bridges specify analyzers. They really
shouldn't know about them and there are other workable solutions.
Create a mechanism to allow custom class and field bridges to specify
analyzers for all fields added to document
----------------------------------------------------------------------------------------------------------------
Key: HSEARCH-664
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-664
Project: Hibernate Search
Issue Type: New Feature
Components: engine
Affects Versions: 3.3.0.Final
Reporter: Hardy Ferentschik
Currently there is no easy way to specify which analyzer to use for custom fields added
via class or custom field bridges. One work around is to write/use a custom scoped
analyzer and use it in conjunction which the bridge. Another work around is the use of
_@ClassBridges_ with mutiple _@ClassBridge_.
Using the query DSL one has to use _overridesForField_ to overcome the issue at query
time.
A more detailed discussion of the issue can be found on the Search forum -
https://forum.hibernate.org/viewtopic.php?f=9&t=1008943&start=0
Possible solutions are:
* Extension of bridge api
* Introduction of a concept similar to _AnalyzerDiscriminator_ which only operates on
field names. _AnalyzerDiscriminator_ depends on the entity state and is really only used
during indexing. At search time this concept cannot be used, because there is no actual
instance to pass to the query
--
This message is automatically generated by JIRA.
For more information on JIRA, see: