Deploy Solr to Production: guides, best practices

Hi everyone! I was looking for full-text search engine and chosen Solr. Quickly introduced with Solr. Now I'm having troubles with taking Solr to Production under Windows Server. As You know, from Solr 5 there is no .WAR-file in package; I couldn't deploy Solr 7.1 to Tomcat 9. Didn't found any in

Schemaless detecting multivalued fields

Hi, I know about the schemaless configuration defaulting to multivalued fields of the corresponding type. I was just wondering if there was a way to first detect if the incoming value is list or singleton, and based on it pick the corresponding types. Ideally if the value is an long then use tlong

Re: Accent insensitive search for greek characters

Hi Alexandre, Thank you so much for the kind response. i will check it out. -- Regards, Chitra

Solr nodes going into recovery mode and eventually failing

Hi, I'm having this weird issue where Solr nodes suddenly go into recovery mode and eventually failing. That one failure kicks off a cascading effect and impacts the other nodes eventually. Without a restart, the entire cluster goes into a limbo after a while. Looking into the log and SPM monito

Goal: reverse chronological display Methods? (1) boost, and/or (2) disable idf

Hello and thanks in advance, I have inherited a working Solr installation, and I want to tune the order of display (score) of search results. I've read a fair amount of documentation, and not found a solution. I have debug output to paste in here, below. On aspect of my site is sort of a curren

Re: TermsQuery Result Ordering

bq: Can I boost the Terms in the terms query I'm pretty sure you can't. But how many of these do you have? You can always increase the maxBooleanClauses limit in solrconfig.xml. It's primarily there to say "having this many clauses is usually a bad idea, so proceed with caution". I've seen 10,000

Re: Jetty maxThreads

Actually, Java 8 defaults to 1MB for each stack thread. -Xsssize Sets the thread stack size (in bytes). Append the letter k or K to indicate KB, m or M to indicate MB, g or G to indicate GB. The default value depends on the platform: Linux/ARM (32-bit): 320 KB Linux/i386 (32-bit): 320 KB Linu

Re: Jetty maxThreads

With an 8GB heap, I’d like to keep thread stack memory to 2GB or under, which means a maxThreads of 1000. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Oct 18, 2017, at 1:41 PM, Walter Underwood wrote: > > Jetty maxThreads is set to 10,000 which

Jetty maxThreads

Jetty maxThreads is set to 10,000 which seams way too big. The comment suggests 5X the number of CPUs. We have 36 CPUs, which would mean 180 threads, which seems more reasonable. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog)

Re: Querying fields that don't exist in every collection

Well, it makes sense however for most use cases. Lets say you have a normal user enter a query WATER:WHEN IS IT NOT A LIQUID if it was interpreted strictly it would throw an error unless WATER is a field, and "NOT" needs to be turned into "not" as well. On Wed, Oct 18, 2017 at 3:46 PM, Beach, Dan

RE: Querying fields that don't exist in every collection

Yes, that appears to be true unless I'm missing something obvious. It seems like in this case Solr should either 1) search against the fields that it /does/ know about in a given collection normally, or 2) return an error. That would be more intuitive than returning results but with different se

Re: Querying fields that don't exist in every collection

I may be wrong here, but what i think is happening is the edismax parser sees a field that doesn't exist, and therefore "believes" all logic you entered into the query is a complete mistake and negates it as such. so NOT becomes the word not and * becomes whitespace. On Wed, Oct 18, 2017 at 3:15

Querying fields that don't exist in every collection

Hello all, I'm running into an issue where adding a field to the qf changes the parsed query if that field doesn't exist in the Solr index. Our use case for doing this is that we have multiple collections and many of our queries leverage aliases to search across several of them simultaneously.

Re: Trying to fix Too Many Boolean Clauses Exception

On Wed, Oct 18, 2017 at 12:23 PM, Erick Erickson wrote: > What have you tried? And what is the current setting? > > This usually occurs when you are assembling very large OR clauses, > sometimes for ACL calculations. > > So if you have a query of the form > q=field:(A OR B OR C OR) > or >

Re: LTR 'feature' and passing date parameters

Thank you very much Binoy. This worked perfectly. Best regards, Dariusz Wojtas On Wed, Oct 18, 2017 at 5:06 PM, Binoy Dalal wrote: > Dariusz, > This problem is most probably occurring because solr does not store dates > in the format you've specified. It's something like: 2017-10-08T12:23:00Z.

TermsQuery Result Ordering

I have an application which currently uses a boolean query. The query could have a large number of boolean terms. I know that the TermsQuery doesn't have the same limitations as the boolean query. However I need to maintain the order of the original terms. The query terms from the boolean query ar

Re: Trying to fix Too Many Boolean Clauses Exception

What have you tried? And what is the current setting? This usually occurs when you are assembling very large OR clauses, sometimes for ACL calculations. So if you have a query of the form q=field:(A OR B OR C OR) or fq=field:(A OR B OR C OR) change it to use TermsQueryParser, see

Re: LTR 'feature' and passing date parameters

Dariusz, This problem is most probably occurring because solr does not store dates in the format you've specified. It's something like: 2017-10-08T12:23:00Z. You'll probably need to specify your date in your efi feature in the manner above to get it to work. You can find more details on dates here

Trying to fix Too Many Boolean Clauses Exception

Hello, Please I have unsuccessfuly tried to fix this error on Solr 6.4. I have increased value to some max, but the same error appear. Please, could you help me. Regards, Patrick R. TOKOUO Mob: (+237) 6 90 08 55 95 Skype: ptokouo In: www.linkedin.com/in/patricktokouo

Certificate issue

Jack, Are you still having the same issue? Thank you, Kent Younge Systems Engineer USPS MTSC IT Support 600 W. Rock Creek Rd, Norman, OK  73069-8357 O:405 573 2273 -Original Message- From: Younge, Kent A - Norman, OK - Contractor [mailto:kent.a.you...@usps.gov.INVALID] Sent: Mo

Re: [ANNOUNCE] Apache Solr 6.6.2 released

You can now access them. Thanks for your patience and understanding. On 18 Oct 2017 3:15 pm, "Ishan Chattopadhyaya" wrote: > Hi Bernd, > > > I get something like "permissionViolation=true", even after login!!! > This is due to the security sensitive nature of those issues. Only PMC > members hav

LTR 'feature' and passing date parameters

Hi, I am using the LTR functionality (SOLR 7) and need to define a feature that will check if the given request parameter of type date (ie. '1998-11-23') matches birthDate in the stored document. Date granularity should be on DAY level. Simply: * if dates match - return 1 * otherwise (birthDate not

Re: zero-day exploit security issue

The JIRA issues are now publicly viewable: https://issues.apache.org/jira/browse/SOLR-11482 https://issues.apache.org/jira/browse/SOLR-11477 On Wed, Oct 18, 2017 at 4:49 AM, Ishan Chattopadhyaya wrote: > There will be a 5.5.5 release soon. 6.6.2 has just been released. > > On Mon, Oct 16, 2017

Re: Concern on solr commit

On Wed, Oct 18, 2017 at 5:09 AM, Leo Prince wrote: > Is there any known negative impacts in setting up autoSoftCommit as 1 > second other than RAM usage..? Briefly: Don't use autowarming (but keep caches enabled!) Use docValues for fields you will facet and sort on (this will avoid using FieldCac

Re: AW: Howto verify that update is "in-place"

According to the concept of immutability that should drive Lucene segmenting approach, I think Emir observation sounds correct. Being docValues a column based data structure, stored on segments i guess when an in place update happens it does just a re-index of just that field. This means we need t

Re: Influencing representing document in grouped search.

If you add a filter query to your original query : fq=genre:A You know that your results ( group heads included) will just be of that genre. So I think we are not getting your question properly. Can you try to express your requirement from the beginning. Leave outside grouping or field collapsing

Intermittent issue in solr index update

Hi, I am facing "Cannot talk to ZooKeeper" issue intermittently in solr index update. While facing this issue strange thing is that there is no error in ZooKeeper logs and also all shards are showing active in solr admin panel. Please find below details logs and Solr server configuration. L

Re: zero-day exploit security issue

There will be a 5.5.5 release soon. 6.6.2 has just been released. On Mon, Oct 16, 2017 at 8:17 PM, Keith L wrote: > Additionally, it looks like the commits are public on github. Is this > backported to 5.5.x too? Users that are still on 5x might want to backport > some of the issues themselves s

Re: [ANNOUNCE] Apache Solr 6.6.2 released

Hi Bernd, > I get something like "permissionViolation=true", even after login!!! This is due to the security sensitive nature of those issues. Only PMC members have access to those issues at the moment. Please revisit those issues after Solr 5.5.5 release to see if you can access them. > Is SOLR

Re: Concern on solr commit

Hi Yonik, Thank you for the inputs. When checked, Upgrading Solr and trying out commitWithin takes a lot of code change from the existing application codebase, hence we are planning to use autoSoftCommit as 1 second and maintaining autoCommit as 15 seconds. So we can maintain our NRT demands. He

Re: [ANNOUNCE] Apache Solr 6.6.2 released

Thanks, but I tried to access the mentioned issues of https://lucene.apache.org/solr/6_6_2/changes/Changes.html https://issues.apache.org/jira/browse/SOLR-11477 https://issues.apache.org/jira/browse/SOLR-11482 I get something like "permissionViolation=true", even after login!!! Is SOLR going to

[ANNOUNCE] Apache Solr 6.6.2 released

18 October 2017, Apache Solr™ 6.6.2 available The Lucene PMC is pleased to announce the release of Apache Solr 6.6.2 Solr is the popular, blazing fast, open source NoSQL search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted

Re: AW: Howto verify that update is "in-place"

Hi, Not claiming that is the case here, but I think I've read some comments (I think in some Jira) that suggest that inplace updates are not as cheap as one might think and that does not reindex dox but dies rewrite of doc values for the segment. Did not look at code, but if someone is familiar wit