Hello Jochen
What are your tokenizers? I guess it should be 'KeywordTokenizerFactory'. To fully
understand, you might send the whole analyzer chain.
But there might be a simple mistake in your pattern, character classes are enclosed by
square brackets. We do a replace of all non-alphanumeric
whitespace using \s nothing happens.
@Oliver: we dont want replace the : in the query ... it is a part of our
callnumbers.
Greetings
Jochen
Oliver Schihin schrieb:
Hello Jochen
What are your tokenizers? I guess it should be 'KeywordTokenizerFactory'. To
fully
understand, you might send the whole
Hello
Our application (VuFind, a library discovery tool) is speaking to a solr 3.5 index per
default. To get the facet values back, the param 'facet.sort' is sent in the request with
an empty value. Solr then delivers the called facets sorted by count, as it should be. A
request looks
You are not using a string type, but a TextField. And in your analysis chain,
standardtokenizer strips the number sign (or #). You can check this in the
analysis part
of the solr backend.
You can either use a string type for seaches like C#, C++ and the like, or map
the
characters to something
Hello
According to release notes from 4.0.0-ALPHA, SOLR-2396, I replaced
ICUCollationKeyFilterFactory with ICUCollationField in our schema. But this throws an
exception, see the following excerpt from the log:
Jul 16, 2012 5:27:48 PM
Hello
According to release notes from 4.0.0-ALPHA, SOLR-2396, I replaced
ICUCollationKeyFilterFactory with ICUCollationField in our schema. But this throws an
exception, see the following excerpt from the log:
Jul 16, 2012 5:27:48 PM
Hello
We are working with solr 4.0, the spellchecker used is still the classic
IndexBasedSpellChecker. Now every time I do a commit, it rebuilds the
spellchecker index, even though I clearly state a build on optimize. The
configuration in solrconfig looks like this:
I call commits testwise
Hello list
My documents come with a field holding a date, always a year:
year2008/year
In the schema, this content is taken for a field year as an integer, and it will be
searchable.
Through a copyfield-instruction I move the year to a facet_year-field, you guess, to
use it for faceting and
