[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-434?pag...
]
G Fernandes commented on HSEARCH-434:
-------------------------------------
Regarding NumericFields, only two params are need: precision and type, probably the type
can be taken from the property?
Also, the simple fact of supporting NumericFields provide a simple but efficient geo
search, which covers the use case of searching all documents that are inside a box given
by a pair of (lat,long). I've not used much Spatial Lucene, but AFAIK the cartesian
tier modality need just one (advanced) configuration: the prefix of the name of the new
internal fields that'll be created at index time to store the coordinates of the point
in the several zoom levels. But that is not part of the field definiton itself, it's
rather a global property for the index.
Btw, this issue was created as a task of Lucene 3.0 migration, but NumericFields are
supported in Lucene 2.9 as well
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira