| java.lang.Object | |
| ↳ | org.apache.lucene.util.FieldCacheSanityChecker.InsanityType |
Class Overview
An Enumeration of the different types of "insane" behavior that may be detected in a FieldCache.
See Also
Summary
| Fields | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| EXPECTED | Indicates an expected bit of "insanity". | ||||||||||
| SUBREADER | Indicates an overlap in cache usage on a given field in sub/super readers. | ||||||||||
| VALUEMISMATCH | Indicates entries have the same reader+fieldname but different cached values. |
||||||||||
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
Fields
public static final FieldCacheSanityChecker.InsanityType EXPECTED
Indicates an expected bit of "insanity". This may be useful for clients that wish to preserve/log information about insane usage but indicate that it was expected.
public static final FieldCacheSanityChecker.InsanityType SUBREADER
Indicates an overlap in cache usage on a given field in sub/super readers.
public static final FieldCacheSanityChecker.InsanityType VALUEMISMATCH
Indicates entries have the same reader+fieldname but different cached values. This can happen if different datatypes, or parsers are used -- and while it's not necessarily a bug it's typically an indication of a possible problem.