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

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik edited comment on HSEARCH-664 at 1/10/11 10:12 AM:
---------------------------------------------------------------------

@Sanne I think I see where you are heading with this, but can you elaborate a bit. It feels like this would be a quite big code change. WDYT?
Personally I thought so far about an additional interface bridges can implement which allows to get more meta information about the fields generated (and in this particualr case also about which analyzer to use per field). This API could then be helpful in eg dirty field checking and the creation of an meta api.
Btw, your idea might cover the dirty check and meta api as well. Not sure!?

      was (Author: hardy.ferentschik):
    @Sanne I think I see where you are heading with this, but can you elaborate a bit. It feels like this would be a quite big code change. WDYT?
Personally I thought so far about an additional interface bridges can implement which allows to get more meta information about the fields generated (and in this particualr case also about which analyzer to use per field). This API could then be helpful in eg dirty field checking and the creation of an meta api.
  
> 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