[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-434?pag...
]
G Fernandes commented on HSEARCH-434:
-------------------------------------
Another option is to extend @Field with numeric attributes:
{code}
@Field(type=FieldType.NUMERIC, precisionStep=8)
{code}
FieldType being enum of STRING, NUMERIC for the moment. The drawback is that @Field will
not be always semantically correct (Numeric related attributes could appear in non numeric
Fields types), but this should keep the API closer to the current one.
Regarding spatial fields, are you planning on using Lucene's spatial Cartesian Tier
system? Geohash? Both? None? :) Any open issues for that?
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