Yes, and I've spend numerous hours configuring and reconfiguring, and
eventually even starting over, but still have not getting it to work
right. Even now, I'm getting bizarre results. For example, I query
"NOTE: This is purely as an example." and I get back really bizarre
suggestions, like "n ot e" and "n o te" and "n o t e" for the first word
which isn't even misspelled! The same goes for "purely" and "example"
also! Moreover, I get extended results showing the frequencies of these
suggestions being over 2600 occurrences, when I'm not even using an
indexed spell checker. I'm only using a file-based spell checker
(/usr/shar/dict/words), and the wordbreak checker.
At this point, I can't even figure out how to narrow down my confusion
so that I can post concise questions to the group. But I'll get there
eventually, starting with removing the wordbreak checker for the
time-being. Your response was encouraging, at least.
Mark
On 10/1/2015 9:45 AM, Alexandre Rafalovitch wrote:
Hi Mark,
Have you gone through a Solr tutorial yet? If/when you do, you will
see you don't need to code any of this. It is configured as part of
the web-facing total offering which are tweaked by XML configuration
files (or REST API calls). And most of the standard pipelines are
already pre-configured, so you don't need to invent them from scratch.
On your specific question, it would be better to ask what _business_
level functionality you are trying to achieve and see if Solr can help
with that. Starting from Lucene code is less useful :-)
Regards,
Alex.
----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 1 October 2015 at 07:48, Mark Fenbers <mark.fenb...@noaa.gov> wrote:
