UnifiedHighlighter returns an error when setting hl.maxAnalyzedChars=-1

Hi, I faced UnifiedHighlighter error when setting hl.maxAnalyzedChars=-1 in Solr 7.6. Here is the procedure for reproducing. $ bin/solr -e techproducts $ curl -XGET "localhost:8983/solr/techproducts/select?hl.fl=name=-1=unified=on=memory=name" I have written a patch to replace negative values

Re: How to debug empty ParsedQuery from Edismax Query Parser

EchoParams=all May also be helpful to pinpoint differences in params from all sources, including request handler defaults. Regards, Alex On Thu, Dec 27, 2018, 8:25 PM Shawn Heisey On 12/27/2018 10:47 AM, Kay Wrobel wrote: > > Now starting from SOLR version 5+, I receive zero (0) results

Re: How to debug empty ParsedQuery from Edismax Query Parser

On 12/27/2018 10:47 AM, Kay Wrobel wrote: Now starting from SOLR version 5+, I receive zero (0) results back, but more importantly, the Query Parser produces an empty parsedQuery. Here is the same query issued to SOLR 7.6.0 (current version): https://pastebin.com/XcNhfdUD

How to debug empty ParsedQuery from Edismax Query Parser

Hi everyone. I have the task of converting our old SOLR 4.10.2 instance to the current SOLR 7.6.0 version. We're using SOLR as our Search API backend for a Drupal 7 Commerce web site. One of the most basic queries is that a customer would enter a part number or a portion of a part number on

Re: Zookeeper timeout issue -

Hi Jan, Setup Details Mach-1 -->20Gb RAM. Apps running :OracleDb,WeblogicServer(services deployed to call solr),*OneSolr Node*,*One Zookeeper node* Mach-2 -->20Gb RAM Apps running :*One Solr Node*,*Two zookeeper nodes*. Solr collection details : ~8k docs,~140MB size on disc,One shard on machine

Re: Starting optimize... Reading and rewriting the entire index! Use with care

1> Not sure. You can get stats after the fact if that would help. 2, 3, 4> Well, optimize is a configuration parameter in DIH that defaults to true so set it false and you'll get rid of the optimize. See:

Re: Solr reload process flow

You can set it in solr.xml, see: http://lucene.apache.org/solr/guide/7_6/format-of-solr-xml.html if you'd like to experiment with bumping it higher. As for "stumbling around in the code" what this _sounds_ like is some kind of deadlock and bumping the number of threads would be, at best, a

Re: Nested Child document doesn't return in query

it might be checked with explainOther request param On Mon, Dec 17, 2018 at 9:08 PM Stephon Harris < shar...@enterprise-knowledge.com> wrote: > I ingested some nested documents into a Solr 7.4 core . When I search with > the following it's not returning a child document that I expected: > > > >

CloudSolrClient with implicit route and disable distributed mode routes to unexpected cores

Hi all, Found interesting problem in Solr 7.5.0 regarding implicit router when _route_ param being provided in non-distributed request. Imagine following set-up... 1. Collection: foo 2. Physical nodes: nodeA, nodeB 3. Shards: shard1, shard2 4. Replication factor: 2 (pure NRT) - nodeA --

Re: MoreLikeThis & Synonyms

On Wed, Dec 26, 2018 at 09:09:02PM -0800, Erick Erickson wrote: > bq. However multiword synonyms are only compatible with queryTime synonyms > expansion. > > Why do you say this? What version of Solr? Query-time mult-word > synonyms were _added_, but AFAIK the capability of multi-word synonyms >

Re: Solr reload process flow

Hi! (Solr 7.6 , Tlog replicas) I have an issue while reloading collection with 100 shards and 3 replicas per shard residing on 5 nodes. Configuration of that collection is pretty complex (90 external file fields) When node starts cores load always successfully. When I reload collection with

ConcurrentUpdateSolrClient - notify on success/failure?

I am trying to figure out if i can log anything or fire some events for other listeners (like a jee event and so on) once ConcurrentUpdateSolrClient sends the updates to the Solr (i.e internal queue is emptied and the request is made with the all of the data to Solr itself) from java code... I am