Re: Use case for the Shingle Filter

The query parser will split on whitespace. I'm not sure how I can use the shingle filter in my query, and use-cases for it. For example, if my fieldType looks like this: ** and I have a document that has "my babysitter is terrific" in the content_t field, a q

Custom DelegatingCollector : collect sorted docs by score

Hi , I developped a custom DelegatingCollector in which I should receive the documents (in collect method) sorted by score. I used SolR 5.5.3. In the older version of SolR, there was a method called acceptsDocsOutOfOrder() . Best Regards --Jamel -- View this message in context: http://luc

Learning to rank - Bad Request

Hi all, I've been trying to get learning to rank working on our own search index. Following the LTR-readme (https://github.com/bloomberg/lucene-solr/blob/master-ltr/solr/contrib/ltr/example/README.md) I ran the example python script to train and upload the model, but I already get an error du

Conditions for replication to copy full index

Hi all, We've recently had some issues with a 5.1.0 core copying the whole index when it was set to replicate from a master core. I've read that if there are documents that have been added to the slave core by mistake, it will do a full copy. Though we are still investigating, this is probably no

Re: Conditions for replication to copy full index

We need to be pretty nit-picky here. bq: do a full copy of an index instead of only the necessary files It's all about "necessary files". "necessary" here means a all changed segments. Since segments are not changed after a commit, then replication can safely ignore any segments files it already

Re: Conditions for replication to copy full index

Thanks Erik. I love Mike's video on segment merging. However I do not believe a large number of merged segments or accidental optimization is the issue. The data in the core is mostly static and there is no evidence so far of a large number of merges that took place. Usually the only updates the i

Re: Does {!child} query support nested Queries ("v=")

Hi Mikhail, Sorry I didn’t reply sooner Here are some example docs - each document for a userAccount object has 1 or more nested documents for our userLinkedAccount object SolrInputDocument(fields: [type=userAccount, typeId=userAccount/HERE-8ce41333-7c08-40d3-9b2c-REDACTED, id=userAccount/HERE

Recommendation for production SOLR

Given the known issues with 6.4.1 and no release date for 6.4.2, is the best recommendation for a production version of SOLR 6.3.0? Hoping to take to production in first week of April. Notice: This email and any attachments are confidential and may not be used, published or redistributed withou

Re: Recommendation for production SOLR

We are going to production this week using 6.3.0. We don’t have time to re-run all the load benchmarks on 6.4.2. We’ll qualify 6.4.2 in a couple of weeks, then upgrade prod if it passes. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Mar 6, 2017, a

Re:Learning to rank - Bad Request

Hi Vincent, Would you be comfortable sharing (redacted) details of the exact upload command you used and (redacted) extracts of the features json file that gave the upload error? Two things I have encountered commonly myself: * uploading features to the model endpoint or model to the feature en

question related to solr LTR plugin

Hi, I do have a question related to solr LTR plugin. I have a use case of personalization and wondering whether you can help me there. I would like to rerank my query based on the relationship of searcher with the author of the returned documents. I do have relationship score in the external d

Re: Recommendation for production SOLR

6.4.2 has passed the vote to release, so it should be hitting the mirrors in a few days at most. On Mon, Mar 6, 2017 at 11:50 AM, Walter Underwood wrote: > We are going to production this week using 6.3.0. We don’t have time to > re-run all the load benchmarks on 6.4.2. > > We’ll qualify 6.4.2 i

Getting an error: was indexed without position data; cannot run PhraseQuery

We keep getting this in our Tomcat/SOLR Logs and I was wondering if a simple schema change will alleviate this issue: INFO - 2017-03-06 07:26:58.751; org.apache.solr.core.SolrCore; [Client_AdvanceAutoParts] webapp=/solr path=/select params={fl=candprofileid,+candid&start=0&q=*:*&wt=json&fq=iss

negative array size exception

After migrating from solr to a load balanced solrcloud with 3 ZKs on the same machines and solr has 3 shards (one per node) We see this logged in the UI on one of our solrs. Does anyone know what this is symptomatic of? java.lang.NegativeArraySizeException at org.apache.lucene.util.Prio

Re: Getting an error: was indexed without position data; cannot run PhraseQuery

Usually an _s field is a "string" type, so be sure you didn't change the definition without completely re-indexing. In fact I generally either index to a new collection or remove the data directory entirely. right, the field isn't indexed with position information. That combined with (probably) th

RE: Getting an error: was indexed without position data; cannot run PhraseQuery

Hmm. We haven’t changed data or the definition in YEARS now. I'll have to do some more digging I guess. Not sure re-indexing is a great thing to do though since this is a production setup and the database for this user is @ 50GB. It would take quite a long time to reindex all that data from

Re: Getting an error: was indexed without position data; cannot run PhraseQuery

You're in a pickle then. If you change the definition you need to re-index. But you claim you haven't changed anything in years as far as the schema is concerned so maybe you're going to get lucky ;). The error you reported is because somehow there's a phrase search going on against this field. Y

RE: Solrcloud after restore collection, when index new documents into restored collection, leader not write to index.

I couldn't find an issue for this in JIRA so I thought I would add some of our own findings here... We are seeing the same problem with the Solr 6 Restore functionality. While I do not think it is important it happens on both our Linux environments and our local Windows development environments.