Hi,
I wrote suggester based on AnalyzingInfixSuggester that deduplicates data on
defined key pattern.
Source code is on github: https://github.com/hlavki/solr-unique-suggester[1]
m.
[1] https://github.com/hlavki/solr-unique-suggester
The Luke request handler may do what you are asking for already? This
is coming directly from Lucene and doesn't rely on what Solr has in
the schema information.
/admin/luke
https://lucene.apache.org/solr/guide/7_7/implicit-requesthandlers.html
https://cwiki.apache.org/confluence/display/SOLR/Luk
I was just looking at the Schema Browser for one of our collections. It's
pretty handy. I was thinking that it would be useful to create a tool that
would create a report about what fields were indexed had docValues, were
multivalued etc...
Has someone built such a tool? I want it to aid in est
Agreed, leave the stopwords alone. I ran into this same problem
thirteen years ago at Netflix. Even before that, I wasn’t removing
stopwords, but I accidentally left them in the Solr 1.3 config.
https://observer.wunderwood.org/2007/05/31/do-all-stopword-queries-matter/
wunder
Walter Underwood
wu
Hi,
We run a SaaS and have a Solr Cloud setup in our cloud. We are developing a
client-side application. We want to have a local copy of the client's
documents stored in Solr. Here, the client's documents are identified from
a particular field in the document e.g. client_id.
I was searching for s
1> why use stopwords at all? They’re largely a holdover from the
bad old days when memory was limited. I usually recommend
people just start by not using stopwords at all.
2> assuming <1> doesn’t work for you, why doesn’t it look feasible
to remove here from the stopword list? True
Ah, understood. It always looks better to be able to say
“I’ve tried it and this is what I found” than “Uh, I’ll have
to get back to you on that” ;)
I’ve occasionally been able to assuage clients like that
by pointing out that often, especially with Open Source,
announcing end of support is often
Thanks, Erick. I'll give it a go this weekend and see how it behaves.
I'll report back so there's a record of my attempts in case anyone else
ends up asking the same question.
Some of our customers get a bit nervous when software goes out of
support, even if it works fine, so I try to be prepared
The property feature didn't work for me. I wanted to spawn Tlog types on
certain nodes and pull on others. I started nodes with a type key with
values TLOG and PULL but that didn't work
I didn't probe further but followed a workaround with starting solr on a
certain port where I wanted tlogs and a
Hi All,
We are using stopword filter factory at both index and search time, to omit
the stopwords.
However, for a one particular case, we are getting "here" as a search query
and "here" is one the words in title/name representing our client.
We are returning zero results as "here" is one of the E
All it means is that there won’t be upgrades/improvements to
ZK, 3.4 will still run. So there’s no need to move to 3.5 independent
of upgrading Solr just because that version of ZK is unsupported
going forward.
I haven’t personally tried to run 3.5 against an earlier version, but
one thing you’ll
Hey folks,
The ZK team just announced that they're dropping 3.4 support as of the
1st of June, 2020.
What does this mean for those of us still on Solr < 8.2? From what I can
tell, ZooKeeper 3.5+ does not work with older Solr versions.
Has anyone managed to get a 3.5+ to work with Solr 7 at all?
12 matches
Mail list logo
