[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-763) Index numeric properties by using @NumericField by default

[Sanne Grinovero (JIRA)]

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

Sanne Grinovero commented on HSEARCH-763:
-----------------------------------------

Main reason to open this issue was to track the decisions taken in mail having subject "[hibernate-dev] Hibernate Search 3.5 or 4". I wrote this proposal and nobody seemed to comment about this point, so maybe it wasn't clear enough.

I think it makes sense as this is a better approach both for
a) sorting (doesn't require padding, so works out of the box)
b) range queries.

I'm not aware of drawbacks of using them, but maybe there is some reason to still use a traditionally string-encoded number? It's known that NumericFields use slightly more space, but being this a possible performance optimization with some drawbacks I'd assume that by default it should take this space.

> Index numeric properties by using @NumericField by default
> ----------------------------------------------------------
>
>                 Key: HSEARCH-763
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-763
>             Project: Hibernate Search
>          Issue Type: Improvement
>            Reporter: Sanne Grinovero
>             Fix For: 4.0.0.Alpha1
>
>
> this will likely imply the need for an option to disable the feature, to index as we did before.

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