Hi,
I'm trying to migrate from Solr 5.1 to Solr 5.2.1. However, I faced some
problems when I'm trying to migrate my index over, and when I'm trying to
link up the external ZooKeeper to Solr.
I'm using ZooKeeper 3.4.6
In Solr 5.1, I used this command to start Solr for both Shard1 and Shard2:
java
Thanks Steve! Everything works now.
A little modification:
"analyzer":{
"charFilters": [ {"class":"solr.MappingCharFilterFactory",
"mapping":"mapping-ISOLatin1Accent.txt"} ],
"tokenizer": {"class":"solr.StandardTokenizerFactory"},
"filters": [{"class"
I tried to setup an autosuggest feature with multiple dictionaries for
title , author and publisher fields.
I used the solr.EdgeNGramFilterFactory to optimize the performance of the
auto suggest.
I have a document in the index with title: Romana.
When I test the text analysis for auto suggest (o
Facets are collected over _tokens_, so the idea
of a token containing a space is kind of odd. You
_might_ be able to get past the parsing error by
escaping the space.
But I doubt that's what you want. I'm assuming that
the field is a text field, broken up by whitespace
or similar. In that case, th
Hi Søren,
> On Jul 3, 2015, at 4:27 AM, Søren wrote:
>
> Thanks Steve! Everything works now.
> A little modification:
>
>"analyzer":{
>"charFilters": [ {"class":"solr.MappingCharFilterFactory",
> "mapping":"mapping-ISOLatin1Accent.txt"} ],
>"tokenizer": {"class"
bq: q=bruleedidn't find anything. It goes into to the raw index I guess
The first thing to do in this case is add &debug=query to the URL and look
at the parsed query near the end of the return packet. In this case it would
look something like
q=default_search_field:brulee
where deault_s
OK, I think you took a wrong turn at the bakery
The FST-based suggesters are intended to look at the
beginnings of fields. It is totally unnecessary to use
ngrams, the FST that gets built does that _for_ you.
Actually it builds an internal FST structure that does
this "en passant".
For gettin
The Suggester “FileDictionaryFactory” resolves the sourceLocation parameter
against the SolrResourceLoader, and in SolrCloud that’s
ZkSolrResourceLoader. The base SolrResourceLoader supports
a solr.allow.unsafe.resourceloading=true system property to be set which
basically allows you to refer to a
Hi Erick, (and Go Blue!)
Thanks for the helpful feedback.
What I was imagining is, if I find all matches with exact term "crib
bedding" in the body or title, then filter out all exact matches in the
body and title, wouldn't it return empty?
Here's the entire query:
http://52.0.110.53:8080/solr/
