Thanks. I have 6.6.2. Do you remember the exact minor version which you
run into with corruptIndex. I did fix it using CheckIndex.
On Sat, Sep 8, 2018 at 2:00 AM Stephen Bianamara
wrote:
> Hmm, when this occurred for me I was also on 6.6 between minor releases. So
> unclear if it's connected t
hi all. we just migrated to cloud on friday night (woohoo!). everything is
looking good (great!) overall. we did, however, just run into a hiccup.
running a query like this got us a 504 gateway time-out error:
**some* *foo* *bar* *query**
it was about 6 partials with encapsulating wildcards that
First of all, wildcards are evil. Be sure that the reason people are
using wildcards wouldn't be better served by proper tokenizing,
perhaps something like stemming etc.
Assuming that wildcards must be handled though, there are two main strategies:
1> if you want to use leading wildcards, look at
Hi Team,
We are using Nutch 1.15 and Solr 6.6.3
We tried crawling one of the URL and and noticed issues while indexing data
to solr.Below is the capture from logs
Caused by:
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at http://localhost:8983/solr/nut
