[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-664) Create a mechanism to allow custom class and field bridges to specify analyzers for all fields added to document

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39523#action_39523 ] 

Sanne Grinovero commented on HSEARCH-664:
-----------------------------------------

I've been wondering if we couldn't convert the output of the DocumentBuilder (the "normal conversion" via annotations) to an runtime-created ClassBridge, so that in the engine we only have to deal with a ClassBridge.

A nice consequence would be that we could have a custom ClassBridge wrap the automatically generated ClassBridge to customize the output: I've had several times the need to write a ClassBridge to add a small customization, and would have been glad to reuse all other fields declared via annotations but ended up to need to re-implement large parts of it.



> 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 _ at ClassBridges_ with mutiple _ at 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.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira