Any other replies to this? Timothy's response was somewhat helpful but hasn't
answered in an authoritative way what the current status of these two different
"forks" of language analyzers is. Surely there is some history here and some
high level status about them? (perhaps I should look at git a
Sorry for the slow response: this one almost fell past the event horizon of
my todo list ;)
Do you mean you are using document blocks (IW.addDocuments) and block
grouping (BlockGroupingCollector)?
Any merge policy is fine with that (merging cannot break up document
blocks), but with index time so
>> I see that it still depends on JTS.
>
> Correction: LatLonPoint most definitely does NOT depend on JTS
I’m sorry this is my mistake, I was using
org.locationtech.spatial4j.context.jts.JtsSpatialContext in my example which
depends on JTS. However I now realize I’m able to switch to
org.loc
On Tue, Jun 7, 2016 at 3:43 PM, Randall Tidd wrote:
With LatLonPoint.newPolygonQuery() it looks like I don’t need Spatial4j at
> all any more either. This makes my case very simple, I only have to index
> LatLonPoint’s and then do a query search with
> LatLonPoint.newPolygonQuery(). I see that
Dear Lucene users,
I have implemented a custom tokenizer (derived from TokenStream).
I need to pass additional attributes to those standard in Lucene
(PositionIncrementAttribute, OffsetAttribute), that would represent the
word position in the tokenized sentence in the number of words and not
char
