[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-41) Allow fine grained analyzers (Entity, attribute, @Field)

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard updated HSEARCH-41:
------------------------------------

    Summary: Allow fine grained analyzers (Entity, attribute, @Field)  (was: Allow different analyzers for each class)

@Analyzer can be in entity, attributes, and individual @Field
the precedence is @Field > attribute > entity > default

> Allow fine grained analyzers (Entity, attribute, @Field)
> --------------------------------------------------------
>
>                 Key: HSEARCH-41
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-41
>             Project: Hibernate Search
>          Issue Type: New Feature
>          Components: mapping
>         Environment: hibernate-search-3.0.0.beta1
>            Reporter: Caleb Land
>            Priority: Minor
>             Fix For: 3.0.0.beta4
>
>
> It would be useful to allow the user to specify different Lucene analyzers to use for each @Indexed class.
> If this is a feature that the hibernate-search developers would be interested in, I wouldn't mind writing tests and implementing it.
> I've hacked together a version of this that works by simply adding a "analyzer" parameter to the @Indexed annotation, and then reading that in SearchFactory in the loop that iterates over the class mappings, but while it suits my purposes, I don't think it's a good, general purpose solution.
> Any ideas?

-- 
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