Ah, Thank you
Turns out it was an experiment, so I removed them any ways and its all good
now.
Since Im here in the configuration for the new 7.x instances I was going to
ask a side question. A lot of my Java properties are old or have been
tweaked over time from a series of different machines,
It looks like there were changes in Lucene 7.0 that limited the size of the
automaton to prevent overflowing the stack.
https://issues.apache.org/jira/browse/LUCENE-7914
The commit being:
https://github.com/apache/lucene-solr/commit/7dde798473d1a8640edafb41f28ad25d17f25a2d
Kevin Risden
On Tue,
For data, its primarily a lot of garbage, around 200k titles, varying
length. im actually looking through my application now to see if I even
still use it or if it was an early experiment. I am just finding it odd
thats its failing in 7 but does fine on 5
On Tue, Apr 3, 2018 at 2:41 PM, Erick Er
What kinds of things go into your title field? On first blush that's a
bit odd for a multi-word title field since it treats the entire input
as a single string. The code is trying to build a large FST to hold
all of this data. Would AnalyzingInfixLookupFactory or similar make
more sense?
buildOnSt
Hey all, I recently got a 7.2 instance up and running, and it seems to be
going well however, I have ran into this when creating one of my indexes,
and was wondering if anyone had a quick idea right off the top of their
head.
solrconfig:
fixspell
FuzzyLookupFactory
string
