Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
-
New
Description
The Intervals has a number of utility methods that provide an IntervalSource for tokens, phrases, etc. But it's missing an important bit: an interval source matching tokens that are a result of some string applied to a full analysis chain. This corresponds to actually resides in the index and is hard to predict from the outside.
This is an important omission in Intervals as a utility class.
I borrowed the implementation from the then-ASL-licensed Elasticsearch code at:
I also modified it slightly to fit the static-method-based Lucene API. I also added a small test that showcases how this method can be used in practice (and why it's hard to accomplish the same result with existing methods).
The only thing I'm not sure is how to attribute Elasticsearch properly - in the notice file, perhaps?
Attachments
Issue Links
- links to