Re: atomic updates in conjunction with optimistic concurrency

Hi, I can't find anything about this in the Solr logs. On the caller side I have this: Error from server at http://x_shard1_replica2: version conflict for x expected=1573538179623944192 actual=1573546159565176832 org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException: Error

Re: mm = 1 and multi-field searches (update)

Interesting. If its working for you then its good but to your original question, qf seems to be working. Adding to mailing list for the benefit of others. On Fri, Jul 21, 2017 at 9:41 AM, Michael Joyner wrote: > Thanks, > > We finally figured out that setting mm=100%

solr.core metric not being reported

Hi all, I am creating a metric under the solr.core group, for arbitrary core names, and I can verify that it does exist programmatically. However, it does not get reported under http://localhost:8983/solr/admin/metrics I do not have a per core xml reporting configuration restricting reporting.

Wildcard query difference

I have a question in terms of how solr/lucene will lookup terms from postings list for the below two queries: 1. a* 2. a*gh My understanding is that for first, it will get all terms starting with 'a' and issue query on those terms. For second, it will again get all terms starting with 'a', then

Re: Wildcard query difference

It's the same in both cases: enumerate all terms that start with "a" and collect them into (conceptually) a huge OR query and execute it. There's been some work lately to avoid the TooManyBooleanClauses exception, but it's still the case that every term starting with "a" has to be examined and

Tika-DIH (zip to xml)

# I am trying to extract zip files(which have xml files in it) using DIH # I can get data and index them from xml like this

Re: finds all documents without a value for field

On 7/20/2017 3:27 PM, Hendrik Haddorp wrote: > If the range query is so much better shouldn't the Solr query parser > create a range query for a token query that only contains the > wildcard? For the *:* case it does already contain a special path. The *:* query is a special string. Although it

[POLL] Solr Plugin Improvements - request for feedback

Hi Solr users and developers, I am currently working on improving Solr’s plugin/contrib system. My goal is to make it a breeze to discover and install plugins and to create a much more vivid 3rd party plugin ecosystem for Apache Solr. If this interests you then I would love to hear your opinion

Re: Solr Issue While indexing Data

By the way you shouldn't be running solr as root. On Fri, Jul 21, 2017 at 12:06 AM, rajat rastogi < rajat.rast...@hindustantimes.com> wrote: > Hi Shawn , > I have Two instances of solr running and my indexing process is in java as > well . > PID 15958 is my indexing process. > PID 4499 is my

Re: Getting IO Exception while Indexing

You may want to dig deeper to see what's going on. It shouldn't be the case. Most likely your code is producing the SolrInputDocument in a different way which is making it fail. You can write SolrInputDocument or print it in json to compare... On Fri, Jul 21, 2017 at 1:31 AM, mesenthil1 <

Re: CDCR - how to deal with the transaction log files

Patrick, Yes! You created default UpdateLog which got written to a disk and then you changed it to CdcrUpdateLog in configs. I find no reason it would create a proper COLLECTIONCHECKPOINT on target tlog. One thing you can try before creating / starting from scratch is restarting source cluster

how to generate code from QueryParser.jj file

Hi, I know that we can make changes in the language by editing QueryParser.jj, however, how does it get generated into java code? Is there any ant target? 'compile' doesn't seem to generate java code for my changes (e.g., adding lower case logical operators). Regards Nawab

Re: how to generate code from QueryParser.jj file

ok, I see there is an `ant javacc` target in some folders, e.g. 1) lucene-solr/solr/build/solr/src-export/solr/core 2) lucene-solr/lucene/queryparser Both of them use different parser files. I am interested in the QueryParser at path:

Re: atomic updates in conjunction with optimistic concurrency

Hendrik, Ran a little test on 6.3, with infinite atomic updates with optimistic concurrency, cannot *reproduce*: List docs = new ArrayList<>(); > SolrInputDocument document = new SolrInputDocument(); > document.addField("id", String.valueOf(1)); > document.addField("external_version_field_s",

Re: atomic updates in conjunction with optimistic concurrency

Thanks for trying to reproduce my issue. I'm using a Solr Cloud, my collection was quite small, only a 50-500 documents, with one shard and a replication factor of 3. I updated all of the documents in one request. Beside that the flow is pretty much like yours. The goal of my code was to

atomic updates in conjunction with optimistic concurrency

Hi, when I try to use an atomic update in conjunction with optimistic concurrency Solr sometimes complains that the version I passed in does not match. The version in my request however match to what is stored and what the exception states as the actual version does not exist in the

Re: atomic updates in conjunction with optimistic concurrency

Hendrik, Can you list down the error snippet so that we can refer the code where exactly that is happening. Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 On Fri, Jul 21,