public class TrieField extends PrimitiveFieldType
NumericField
.
See NumericRangeQuery
for more details.
It supports integer, float, long, double and date types.
For each number being added to this field, multiple terms are generated as per the algorithm described in the above
link. The possible number of terms increases dramatically with lower precision steps. For
the fast range search to work, trie fields must be indexed.
Trie fields are sortable in numerical order and can be used in function queries.
Note that if you use a precisionStep of 32 for int/float and 64 for long/double/date, then multiple terms will not be
generated, range search will be no faster than any other number field, but sorting will still be possible.NumericRangeQuery
Modifier and Type | Class and Description |
---|---|
static class |
TrieField.TrieTypes |
FieldType.DefaultAnalyzer
Modifier and Type | Field and Description |
---|---|
static int |
DEFAULT_PRECISION_STEP |
protected Object |
missingValue |
protected int |
precisionStep |
protected int |
precisionStepArg |
protected TrieField.TrieTypes |
type |
analyzer, args, falseProperties, log, POLY_FIELD_SEPARATOR, queryAnalyzer, trueProperties, typeName
BINARY, INDEXED, MULTIVALUED, OMIT_NORMS, OMIT_POSITIONS, OMIT_TF_POSITIONS, REQUIRED, SORT_MISSING_FIRST, SORT_MISSING_LAST, STORE_TERMOFFSETS, STORE_TERMPOSITIONS, STORE_TERMVECTORS, STORED, TOKENIZED
Constructor and Description |
---|
TrieField() |
Modifier and Type | Method and Description |
---|---|
Fieldable |
createField(SchemaField field,
String externalVal,
float boost)
Used for adding a document when a field needs to be created from a
type and a string.
|
static String |
getMainValuePrefix(FieldType ft)
expert internal use, subject to change.
|
int |
getPrecisionStep() |
Query |
getRangeQuery(QParser parser,
SchemaField field,
String min,
String max,
boolean minInclusive,
boolean maxInclusive)
Returns a Query instance for doing range searches on this field type.
|
SortField |
getSortField(SchemaField field,
boolean top)
Returns the SortField instance that should be used to sort fields
of this type.
|
TrieField.TrieTypes |
getType() |
ValueSource |
getValueSource(SchemaField field,
QParser qparser)
called to get the default value source (normally, from the
Lucene FieldCache.)
|
String |
indexedToReadable(String indexedForm)
Given an indexed term, return the human readable representation
|
protected void |
init(IndexSchema schema,
Map<String,String> args)
subclasses should initialize themselves with the args provided
and remove valid arguments.
|
boolean |
isTokenized()
Returns true if fields of this type should be tokenized
|
boolean |
multiValuedFieldCache()
Returns true if a single field value of this type has multiple logical values
for the purposes of faceting, sorting, etc.
|
String |
readableToIndexed(String val)
Given the readable value, return the term value that will match it.
|
String |
storedToIndexed(Fieldable f)
Given the stored field, return the indexed form
|
String |
storedToReadable(Fieldable f)
Given the stored field, return the human readable representation
|
String |
toExternal(Fieldable f)
Convert the stored-field format to an external (string, human readable)
value
|
String |
toInternal(String val)
Convert an external value (from XML update command or from query string)
into the internal format for both storing and indexing (which can be modified by any analyzers).
|
Object |
toObject(Fieldable f)
Convert the stored-field format to an external object.
|
void |
write(TextResponseWriter writer,
String name,
Fieldable f)
calls back to TextResponseWriter to write the field value
|
void |
write(XMLWriter xmlWriter,
String name,
Fieldable f)
Renders the specified field as XML
|
createField, createFields, getAnalyzer, getArg, getFieldIndex, getFieldQuery, getFieldStore, getFieldTermVec, getIndexOptions, getQueryAnalyzer, getStringSort, getTypeName, getValueSource, hasProperty, isMultiValued, isPolyField, restrictProps, setAnalyzer, setQueryAnalyzer, toString
public static final int DEFAULT_PRECISION_STEP
protected int precisionStepArg
protected int precisionStep
protected TrieField.TrieTypes type
protected Object missingValue
protected void init(IndexSchema schema, Map<String,String> args)
FieldType
init
in class PrimitiveFieldType
public Object toObject(Fieldable f)
FieldType
toObject
in class FieldType
FieldType.toInternal(java.lang.String)
public SortField getSortField(SchemaField field, boolean top)
FieldType
getSortField
in class FieldType
SchemaField.checkSortability()
public ValueSource getValueSource(SchemaField field, QParser qparser)
FieldType
getValueSource
in class FieldType
public void write(XMLWriter xmlWriter, String name, Fieldable f) throws IOException
FieldType
write
in class FieldType
IOException
public void write(TextResponseWriter writer, String name, Fieldable f) throws IOException
FieldType
write
in class FieldType
IOException
public boolean isTokenized()
FieldType
isTokenized
in class FieldType
public boolean multiValuedFieldCache()
FieldType
multiValuedFieldCache
in class FieldType
public int getPrecisionStep()
public TrieField.TrieTypes getType()
public Query getRangeQuery(QParser parser, SchemaField field, String min, String max, boolean minInclusive, boolean maxInclusive)
FieldType
SolrQueryParser
currently passes part1 and part2 as null if they are '*' respectively. minInclusive and maxInclusive are both true
currently by SolrQueryParser but that may change in the future. Also, other QueryParser implementations may have
different semantics.
Sub-classes should override this method to provide their own range query implementation. They should strive to
handle nulls in part1 and/or part2 as well as unequal minInclusive and maxInclusive parameters gracefully.getRangeQuery
in class FieldType
field
- the schema fieldmin
- the lower boundary of the range, nulls are allowed.max
- the upper boundary of the range, nulls are allowedminInclusive
- whether the minimum of the range is inclusive or notmaxInclusive
- whether the maximum of the range is inclusive or notSolrQueryParser.getRangeQuery(String, String, String, boolean)
public String storedToReadable(Fieldable f)
FieldType
storedToReadable
in class FieldType
public String readableToIndexed(String val)
FieldType
readableToIndexed
in class FieldType
public String toInternal(String val)
FieldType
toInternal
in class FieldType
FieldType.toExternal(org.apache.lucene.document.Fieldable)
public String toExternal(Fieldable f)
FieldType
toExternal
in class FieldType
FieldType.toInternal(java.lang.String)
public String indexedToReadable(String indexedForm)
FieldType
indexedToReadable
in class FieldType
public String storedToIndexed(Fieldable f)
FieldType
storedToIndexed
in class FieldType
public Fieldable createField(SchemaField field, String externalVal, float boost)
FieldType
By default, the indexed value is the same as the stored value (taken from toInternal()). Having a different representation for external, internal, and indexed would present quite a few problems given the current Lucene architecture. An analyzer for adding docs would need to translate internal->indexed while an analyzer for querying would need to translate external->indexed.
The only other alternative to having internal==indexed would be to have internal==external. In this case, toInternal should convert to the indexed representation, toExternal() should do nothing, and createField() should *not* call toInternal, but use the external value and set tokenized=true to get Lucene to convert to the internal(indexed) form.
:TODO: clean up and clarify this explanation.createField
in class FieldType
FieldType.toInternal(java.lang.String)