[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-763?pag...
]
Emmanuel Bernard commented on HSEARCH-763:
------------------------------------------
Let me revive this discussion.
I think it's a good idea to move new applications to use @NumericField by default.
But I would like to see how we will:
* support older application without breaking them (maybe a global flag is appropriate)
* how will people be able to use the old non-numeric fields? by explicitly providing a
field bridge?
* Does the current design of @Field / @NumericField works with this new approach
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.Alpha2
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira