Re: Slower queries with 7.3.1?

I did some more (micro)benchmarking with a single query. Setting the query cache size to zero I see 400ms response time on 7.2 and 600ms on 7.3. Running curl in a loop on my laptop. ~4M docs. ~3G index. 1M total hits for the query.. Yup. I'm reluctant to post the query. It has multiple 300+ charact

Re: Different docs order in different replicas of the same shard

On 5/25/2018 11:07 AM, SOLR4189 wrote: > You are right, BUT I have two indexers (one in WCF service and one in HADOOP) > and in two my indexers I'm using atomic updates in each document. According > to Atomic Update Processor Factory >

Re: Different docs order in different replicas of the same shard

You are right, BUT I have two indexers (one in WCF service and one in HADOOP) and in two my indexers I'm using atomic updates in each document. According to Atomic Update Processor Factory and according to your solution (t

Re: Sort by payload value

Hi Erik - Solr is tokenizing correctly as you can see it return the payload field value along with the full payload and they match on the particular field. The field does have a lowercase filter as you can see in the definition. Changing it to single word query doesn't fix it either.. On Fri, May

Re: Sort by payload value

My first guess (and it's a total guess) is that you either have a case problem or you're tokenizing the string. Does your field definition lower-case the tokens? If it's a string type then certainly not. Quick test would be to try your query with a value that matches case and has no spaces, maybe

Re: Different docs order in different replicas of the same shard

On 5/25/2018 7:28 AM, SOLR4189 wrote: > I use SOLR-6.5.1 and I want to start to use replicas. > > For it I want to understand something: > > 1) Can asynchronous forwarding document from leader to all replicas or some > another reasons cause that replica A may see update X then Y, and replica B > ma

Re: simple enrich uploaded binary documents with sha256 hashes

I'd consider using a separate Java program that uses Tika directly, or one of various services. Then you can assemble whatever you please before sending the doc to Solr. There are multiple reasons to recommend this, see: https://lucidworks.com/2012/02/14/indexing-with-solrj/ There are other reason

Re: Different docs order in different replicas of the same shard

For (1), it's not a problem. Every update goes through the leader, where it gets a version stamp (the _version_ field). So if doc1 is updated twice the leader will assign a version stamp. Call the updated doc1.1 and doc1.2. If replica X sees doc1.2 first, it indexes it. If it subsequently sees doc1

Re: Solr streaming - get single value from tuple

Thanks. https://issues.apache.org/jira/browse/SOLR-12401 -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 24. mai 2018 kl. 16:11 skrev Joel Bernstein : > > I've been meaning to add this, so let's create a ticket. Until it's > released you can plugin the function in th

Different docs order in different replicas of the same shard

I use SOLR-6.5.1 and I want to start to use replicas. For it I want to understand something: 1) Can asynchronous forwarding document from leader to all replicas or some another reasons cause that replica A may see update X then Y, and replica B may see update Y then X? If yes, thus a particular

Re: Escaping in streaming expression

I did a little experimentation: This query is sent down to Solr and performs a proper wildcard: search(collection2, q="hel*", fl="id", sort="id asc") This query properly escapes the wildcard: search(collection2, q="hel\*", fl="id", sort="id asc") So it appears that the main issue is with the d

Impact/Performance of maxDistErr

Hello, we are indexing a polygon with 4 points (non-rectangular, field-of-view of a camera) in a RptWithGeometrySpatialField alongside some more fields, to perform searches that check if a point is within this polygon We started using the default configuration found in several examples online

Re: Escaping in streaming expression

Thanks for your help. Yes, I think SOLR-10894 is exactly about the issue I have seen. So if I understand correctly there is currently no way to create a method in client code (like Drupal’s search_api_solr module) that takes arbitrary user input and escapes it to get *always* a valid expression