By looking at the code, it was not too hard to figure out.
The defaults defined in BoostFieldMapper are
public static class Defaults extends NumberFieldMapper.Defaults {
public static final String NAME = "_boost";
public static final Float NULL_VALUE = null;
public static final Field.Index INDEX = Field.Index.NO;
public static final Field.Store STORE = Field.Store.NO;
}
The mapper will ignore any settings defined on the field. Can they be used
as well? It would be easy to add it to the parse method, but not sure if
there are implications.
Cheers,
Ivan
On Fri, Jan 18, 2013 at 12:03 PM, Ivan Brusic ivan@brusic.com wrote:
The code has changed slightly (I am on 0.20RC2), but the issue remains:
public static class Defaults extends NumberFieldMapper.Defaults {
public static final String NAME = "_boost";
public static final Float NULL_VALUE = null;
public static final FieldType FIELD_TYPE = new
On Fri, Jan 18, 2013 at 12:15 PM, Ivan Brusic ivan@brusic.com wrote:
By looking at the code, it was not too hard to figure out.
The defaults defined in BoostFieldMapper are
public static class Defaults extends NumberFieldMapper.Defaults {
public static final String NAME = "_boost";
public static final Float NULL_VALUE = null;
public static final Field.Index INDEX = Field.Index.NO;
public static final Field.Store STORE = Field.Store.NO;
}
The mapper will ignore any settings defined on the field. Can they be used
as well? It would be easy to add it to the parse method, but not sure if
there are implications.
Cheers,
Ivan
On Fri, Jan 18, 2013 at 12:03 PM, Ivan Brusic ivan@brusic.com wrote:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.