Class DirectoryTaxonomyWriter.SinglePositionTokenStream
- All Implemented Interfaces:
Closeable,AutoCloseable
- Enclosing class:
DirectoryTaxonomyWriter
-
Nested Class Summary
Nested classes/interfaces inherited from class org.apache.lucene.util.AttributeSource
AttributeSource.State -
Field Summary
FieldsModifier and TypeFieldDescriptionprivate PositionIncrementAttributeprivate booleanprivate CharTermAttributeprivate intprivate final StringFields inherited from class org.apache.lucene.analysis.TokenStream
DEFAULT_TOKEN_ATTRIBUTE_FACTORY -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionbooleanConsumers (i.e.,IndexWriter) use this method to advance the stream to the next token.voidset(int val) Set the value we want to keep, as the position increment.Methods inherited from class org.apache.lucene.analysis.TokenStream
close, end, resetMethods inherited from class org.apache.lucene.util.AttributeSource
addAttribute, addAttributeImpl, captureState, clearAttributes, cloneAttributes, copyTo, endAttributes, equals, getAttribute, getAttributeClassesIterator, getAttributeFactory, getAttributeImplsIterator, hasAttribute, hasAttributes, hashCode, reflectAsString, reflectWith, removeAllAttributes, restoreState, toString
-
Field Details
-
termAtt
-
posIncrAtt
-
returned
private boolean returned -
val
private int val -
word
-
-
Constructor Details
-
SinglePositionTokenStream
-
-
Method Details
-
set
public void set(int val) Set the value we want to keep, as the position increment. Note that when TermPositions.nextPosition() is later used to retrieve this value, val-1 will be returned, not val.IMPORTANT NOTE: Before Lucene 2.9, val>=0 were safe (for val==0, the retrieved position would be -1). But starting with Lucene 2.9, this unfortunately changed, and only val>0 are safe. val=0 can still be used, but don't count on the value you retrieve later (it could be 0 or -1, depending on circumstances or versions). This change is described in Lucene's JIRA: LUCENE-1542.
-
incrementToken
Description copied from class:TokenStreamConsumers (i.e.,IndexWriter) use this method to advance the stream to the next token. Implementing classes must implement this method and update the appropriateAttributeImpls with the attributes of the next token.The producer must make no assumptions about the attributes after the method has been returned: the caller may arbitrarily change it. If the producer needs to preserve the state for subsequent calls, it can use
AttributeSource.captureState()to create a copy of the current attribute state.This method is called for every token of a document, so an efficient implementation is crucial for good performance. To avoid calls to
AttributeSource.addAttribute(Class)andAttributeSource.getAttribute(Class), references to allAttributeImpls that this stream uses should be retrieved during instantiation.To ensure that filters and consumers know which attributes are available, the attributes must be added during instantiation. Filters and consumers are not required to check for availability of attributes in
TokenStream.incrementToken().- Specified by:
incrementTokenin classTokenStream- Returns:
- false for end of stream; true otherwise
- Throws:
IOException
-