]
Sanne Grinovero updated HSEARCH-810:
------------------------------------
Suitable for new contributors: [Yes, likely]
Affects Version/s: 3.4.0.Final
Fix Version/s: 4.0
@NumericFields with NumericField forName require @Field to use name=
--------------------------------------------------------------------
Key: HSEARCH-810
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-810
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.4.0.Final
Reporter: Izaak Alpert
Priority: Minor
Fix For: 4.0
It seems that unless name for the first @Field is specified range searches on that field
will not be numeric
Doesn't work:
public class TestExampleClass {
@Fields({
@Field( index = Index.UN_TOKENIZED),
@Field(name = "quantityFitted_forSort", index = Index.UN_TOKENIZED, store =
Store.YES) })
@NumericFields({ @NumericField(forField = "quantityFitted") })
private Integer quantityFitted;
}
public class TestExampleClass {
@Fields({
@Field(name = "quantityFitted", index = Index.UN_TOKENIZED),
@Field(name = "quantityFitted_forSort", index = Index.UN_TOKENIZED, store =
Store.YES) })
@NumericFields({ @NumericField(forField = "quantityFitted") })
private Integer quantityFitted;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: