[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-434) Make use of NumericField
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Mon Oct 11 03:35:59 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38683#action_38683 ]
Emmanuel Bernard commented on HSEARCH-434:
------------------------------------------
It's the same discussion we had with one more options basically. But it boils down to extensibility. I am concerned about flat annotations with many irrelevant options in many cases. The options on the table are:
- a fully dedicated @NumericField annotation copying some of the @Field types
- put everything on @Field with the risk of confusing people (esp when new types of types come to the table)
- have an extension annotation ie @Field @NumericField(forField)
- use the same mechanism Bean Validation uses to compose annotations (ie a @NumericField annotated with @Field, @Boost etc)
The last option is quite elegant but I don't think it provides much benefits to the user as I don't see extensibility as a primary feature at this time.
> Make use of NumericField
> -------------------------
>
> Key: HSEARCH-434
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-434
> Project: Hibernate Search
> Issue Type: Sub-task
> Components: engine
> Reporter: Emmanuel Bernard
> Assignee: G Fernandes
> Fix For: 3.3.0
>
>
--
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