UseLargePages

Do you think setting aside 2GB for UseLargePages would generally help indexing or not? I can imaging it might help -- Bill Bell billnb...@gmail.com cell 720-256-8076

Re: Queries not supported by Lucene Query Parser syntax

Hello Leonid, Yep. This problem exists and makes hard the migration from Lucene to Solr. You might be interested in Parboiled http://www.youtube.com/watch?v=DXiRYfFGHJE The simplest way to solve it is to serialize Lucene Query instance into parameter or request body. Unfortunately, Query is not Se

Re: ignoring bad documents during index

Hello, Please find below On Thu, Jan 1, 2015 at 11:59 PM, SolrUser1543 wrote: > 1. If it is possible to ignore such an error and continue to index D4 ? > this can be done by catching and swallowing an exception in custom UpdateRequestProcessor > 2. What will the best way to add an information

RE: poor performance when connecting to CloudSolrServer(zkHosts) using solrJ

While I'm not a net optimization whiz, a properly configured DNS client will "cache" the recent resolved lookups; this way even though you are referring to the Fully Qualified Domain Name (FQDN), the local DNS client will return the recently acquired IP address (within the constraints of the Dom

Re: Garbage Collection tuning - G1 is now a good option

But tons of people on this mailing list do not recommend AggressiveOpts Why do you recommend it? On Thu, Jan 1, 2015 at 12:10 PM, Shawn Heisey wrote: > I've been working with Oracle employees to find better GC tuning > options. The results are good enough to share with the community: > > https

Re: poor performance when connecting to CloudSolrServer(zkHosts) using solrJ

My two cents, do check network connectivity. In past I remember changing the zookeeper server name to actual IP improved the speed a bit. DNS sometimes take time to resolve hostname. Could be worth trying this option. Thanks -Hussain On Mon, Dec 29, 2014 at 6:31 PM, Shawn Heisey wrote: > On 12

ignoring bad documents during index

Suppose I need to index a bulk of several documents ( D1 D2 D3 D4 ) - 4 documents in one request. If e.g. D3 was an incorrect , so exception will be thrown and HTTP response with 400 bad request will be returned . Documents D1 and D2 will be indexed, but D4 not . Also no indication will be retu

Re: SpellCheck (AutoComplete) Not Working In Distributed Environment

Shawn, When running SolrCloud do you even have to include the shards parameter ,shouldnt only shards.qt parameter suffice? On Dec 30, 2014 7:17 PM, "Shawn Heisey" wrote: > On 12/30/2014 5:03 PM, Charles Sanders wrote: > > Thanks for the suggestion. > > > > I did not do that originally because th

Re: Mixing 4.x SolrJ and Solr.war - compatible?

On 1/1/2015 6:34 AM, Gili Nachum wrote: > So, It seems I can't upgrade Solr beyond 4.7 as long as I'm running SolrJ > on Java6 JVM. > With any luck I might be able to compile SolrJ that's newer than 4.7 with > Java6. I'll check that next. > Thanks Shawn. That's very helping! Solr 4.8 and later (co

Garbage Collection tuning - G1 is now a good option

I've been working with Oracle employees to find better GC tuning options. The results are good enough to share with the community: https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning With the latest Java 7 or Java 8 version, and a couple of tuning options, G1GC has grown up enough to be a viable

Re: Queries not supported by Lucene Query Parser syntax

Hi Lenoid, Here is another un-committed parser : https://issues.apache.org/jira/browse/LUCENE-5205 Ahmet On Thursday, January 1, 2015 5:59 PM, Roman Chyla wrote: Hi Leonid, I didn't look into solr qparser for a long time, but I think you should be able to combine different query parsers i

Re: Frequent deletions

Is there a specific list of which data structures are "sparce" and "non-sparce" for Lucene and Solr (referencing G+ post)? I imagine this is obvious to low-level hackers, but could actually be nice to summarize it somewhere for troubleshooting. Regards, Alex. Sign up for my Solr resources

Re: Queries not supported by Lucene Query Parser syntax

Hi Leonid, I didn't look into solr qparser for a long time, but I think you should be able to combine different query parsers in one query. Look at the SolrQueryParser code, maybe now you can specify custom query parser for every clause (?), st like: foo AND {!lucene}bar I dont know, but worth e

Re: Queries not supported by Lucene Query Parser syntax

Yes, you are always limited by the query parser syntax, but of course you can always write your own query parser as well. There is an open issue for an XML-based query parser that would give you greater control. but... it's not committed yet: https://issues.apache.org/jira/browse/SOLR-839 -- Jack

Re: Mixing 4.x SolrJ and Solr.war - compatible?

So, It seems I can't upgrade Solr beyond 4.7 as long as I'm running SolrJ on Java6 JVM. With any luck I might be able to compile SolrJ that's newer than 4.7 with Java6. I'll check that next. Thanks Shawn. That's very helping! On Wed, Dec 31, 2014 at 6:54 PM, Shawn Heisey wrote: > On 12/31/2014 6

Re: Create core problem in tomcat

You may have a field types in your schema that using stopwords.txt file like this: so, you must have files *stopwords_ar.txt* and* stopwords_en.txt* in INSTA

Re: Frequent deletions

Also see this G+ post I wrote up recently showing how %tg deletions changes over time for an "every add also deletes a previous document" stress test: https://plus.google.com/112759599082866346694/posts/MJVueTznYnD Mike McCandless http://blog.mikemccandless.com On Wed, Dec 31, 2014 at 12:21 PM,

Re: Queries not supported by Lucene Query Parser syntax

Hi Leonid, Have you had a look at edismax query parser[1]? Isn't that any use to your requirement? I am not sure whether it is something that you are looking for. But the question seemed to be having a query related to that. [1] http://wiki.apache.org/solr/ExtendedDisMax#Query_Syntax On Th

Queries not supported by Lucene Query Parser syntax

Hello, Are we always limited by the query parser syntax when passing a query string to Solr? What about the query elements which are not supported by the syntax? For example, BooleanQuery.setMinimumNumberShouldMatch(n) is translated by BooleanQuery.toString() into ~n. But this is not a valid query