[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-763?pag...
]
Hardy Ferentschik edited comment on HSEARCH-763 at 9/9/11 3:55 AM:
-------------------------------------------------------------------
{quote}
* 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?
{quote}
I think these two points are important. Especially interesting what happens with existing
apps using already some sort of padding bridge
and the documentation must be clearly aligned (obviously)
was (Author: hardy.ferentschik):
{quote}
* 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?
{quote}
and the documentation must be clearly aligned (obviously)
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.Beta1
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