[hibernate-issues] [Hibernate-JIRA] Created: (HSEARCH-711) Review of org.hibernate.search.annotations.Index API (token names, parameter composition)

Sanne Grinovero (JIRA) noreply at atlassian.com
Thu Mar 10 06:22:08 EST 2011


Review of org.hibernate.search.annotations.Index API (token names, parameter composition)
-----------------------------------------------------------------------------------------

                 Key: HSEARCH-711
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-711
             Project: Hibernate Search
          Issue Type: Deprecation
            Reporter: Sanne Grinovero
             Fix For: 4.0


We're having Enum values labeled NO,TOKENIZED,UN_TOKENIZED,NO_NORMS,..
while Lucene changed these names to more suited "analyzed", "not_analyzed", etc.

Also I think it would be great to use an array of parameters instead of an enum listing all options, or maybe split the option in two:

@Field({ANALYZE,NO_NORMS})

or

@Field(analyze=YES,norms=No)

We should at least deprecate current names and use the more appropriate terms.

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

        


More information about the hibernate-issues mailing list