[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-711) Review of @org.hibernate.search.annotations.Field parameters

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-711?pag... ] Hardy Ferentschik updated HSEARCH-711: -------------------------------------- Description: We're having Enum values labeled _NO_, _TOKENIZED_, _UN_TOKENIZED_, _NO_NORMS_ for the _org.hibernate.search.annotations.Index_ enum 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: {code} @Field({ANALYZE,NO_NORMS}) {code} or {code} @Field(analyze=YES,norms=NO) {code} We should at least deprecate current names and use the more appropriate terms. was: We're having Enum values labeled _NO_, _TOKENIZED_, _UN_TOKENIZED_, _NO_NORMS_, ... 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: {code} @Field({ANALYZE,NO_NORMS}) {code} or {code} @Field(analyze=YES,norms=NO) {code} We should at least deprecate current names and use the more appropriate terms. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira