Re: What's the deal with dataimporthandler overwriting indexes?

I've run into this also; it is a key difference between a master-slave setup and a solrCloud setup. clean=true has always deleted the index on the first commit, but in older versions of Solr, the workaround was to disable replication until the full reindex had completed. This is a convenient

Re: Per-field slop param in eDisMax

To do this you specify the slop on each field when you specify the pf/pf2/pf3 parameters: pf:fieldA~2 fieldB~5 I'll try to add an example to the documentation here: https://lucene.apache.org/solr/guide/7_6/the-extended-dismax-query-parser.html#using-slop Elizabeth On Wed, Jan 23, 2019 at 10:30

Re: Search query with & without question mark

Because the standard query parser treats '?' as a single-character wildcard: https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html So in the case q="how do I add a field", the word "field" in your document matches. In the second case q="how do I add a field?" it is looking for

Re: Solr relevancy score different on replicated nodes

Hello, To a certain extent, I agree with Eric, that this isn't a problem, but looks like one. The nature of TF*IDF is such that you will see different scores for the same query over time on the same replica, or different replicas for the same query with most replication schemes. This is mildly

Re: Integrate nutch with solr

Hi Dinesh, This article is quite old (Nutch 1.x, Solr 4.x), but the high-level steps are still pretty much the same: get your java set up, kick off a Solr , and

Re: Weird behavioural differences between pf in dismax and edismax

That would make sense. Multi-term synonyms get into a weird case too. Should the single-term words that have multi-term synonyms expand out? Or should the multi-term synonyms that have single-term synonyms contract down and count as only a single clause for pf2 or pf3. On Tue, May 29, 2018 at

Re: Weird behavioural differences between pf in dismax and edismax

the documents that have enough terms per mm and documents that have enough terms in one field. Elizabeth Haubert On Tue, May 29, 2018 at 5:14 AM, Alessandro Benedetti wrote: > In my opinion, given the definition of dismax and edismax query parsers, > they > should behave

Re: PF, PF2, PF3 clauses missing in solr7 with query-time synonyms?

Thank you, Elizabeth On Wed, Apr 18, 2018 at 12:38 PM, Elizabeth Haubert < ehaub...@opensourceconnections.com> wrote: > I'm seeing pf and pf3 clauses fail to generate in long queries containing > synonyms. Wondering if anyone else has run into this, or if it needs to

PF, PF2, PF3 clauses missing in solr7 with query-time synonyms?

I'm seeing pf and pf3 clauses fail to generate in long queries containing synonyms. Wondering if anyone else has run into this, or if it needs to be submitted as a bug in Jira. It is a showstopper problem for the current project, as the pf and pf3 were pretty heavily tuned. Using Solr 7.1; all

dataimporthandler ignoring configured timezone for indexStartTime?

I'm getting the incorrect the reported time deltas on the admin console for "indexing since" and "started". It looks like DIH is converting the last start time to UTC: Last Update: 09:57:15 Indexing completed. Added/Updated: 94078 documents. Deleted 0 documents. (Duration: 06s) Requests: 1 ,

Expected response from master when replication is disabled?

What is the intended use case and behavior of disablereplication? My expectation was that it would be to cause the master to not respond to slave requests. Working with a master/slave Solr 7.1 setup; slave is set up to poll every 60s. I would prefer to remain on M/S for immediate future, while