Re: Indexing of documents in more than one step (SOLRJ)

Maciej: you really have two choices: 1> re-index the entire document with fields a, b, c, d, e, f. In that case though, why bother indexing the first time ;) 2> use Atomic Updates: https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents but note the restrictions. Best, Erick

Re: How to get the core index progress/status ?

On 2/15/2017 4:06 PM, Ratan Servegar wrote: > I've been looking everywhere to find a solution for the problem i've > having, I am starting an index on a core by making an ajax call from > my page to the solr server via url. However i want to know the index > start time and completion time and also

How to get the core index progress/status ?

Hello, I've been looking everywhere to find a solution for the problem i've having, I am starting an index on a core by making an ajax call from my page to the solr server via url. However i want to know the index start time and completion time and also i want to know how many records are

[SECURITY] CVE-2017-3163 Apache Solr ReplicationHandler path traversal attack

CVE-2017-3163: Apache Solr ReplicationHandler path traversal attack Severity: Moderate Vendor: The Apache Software Foundation Versions Affected: Solr 1.4 to 6.4.0 Description: When using the Index Replication feature, Solr nodes can pull index files from a master/leader node using an HTTP API

RE: Atomic updates to increase single field bulk updates?

Hello Sebastian, Except for the requirement to have all fields stored, there is from Solr/Lucene's point of view not much difference between indexing a partial update or a complete document. Under the hood a partial update is a complete object anyway. Using partial updates you gain a little

Atomic updates to increase single field bulk updates?

Dear solr users, when updating documents in bulk (i.e. 40.000 documents at once), and only changing the value of a single Boolean-Flag, I currently re-index all whole 40.000 objects. However, the process of obtaining all relevant information for each object from the database is one of

[ANNOUNCE] Apache Solr 5.5.4 released

15 February 2017, Apache Solr™ 5.5.4 available The Lucene PMC is pleased to announce the release of Apache Solr 5.5.4 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,

Re: Getting "Error getting file length for [segments_5]" warnings in Solr 6.4.0

Shawn, We have confirmed that yes, this is just log noise, and possibly related to the admin interface and not the actual indexing process. As for indexing stopping, that was not actually the case. I got confused about how many documents were in the collection I was indexing, and thought there

Re: indent parsedquery_toString

That is not supported. However, you can add debug.explain.structured=true for a more detailed breakdown of the information. Regards, Alex. http://www.solr-start.com/ - Resources for Solr users, new and experienced On 15 February 2017 at 09:03, Gleb wrote: > How to

indent parsedquery_toString

How to make parsedquery_toString more readable? I want read it indented. +( ( (name_text_ru:hello)~0.5 (name_text_ru:word)~0.5 ( (name_text_ru:ложка name_text_ru:trump) )~0.5 )~3 ) -- View

Re: Core replication, Slave not flipping to master

On 2/15/2017 4:06 AM, philippa griggs wrote: > Solr 5.4.1, multiple cores with two cores per shard. Zookeeper 3.4.6 (5 > zookeeper ensemble). > > I have noticed an error with the replication between two cores in a shard. > I’m having to perform a schema update which means I have to stop and

Re: Can SOLR-5730 patch be backported to Solr 5.5.3

On 2/14/2017 2:45 AM, Sahil Agarwal wrote: > Can the patch for jira issue SOLR-5730 be backported to solr 5.5.3?? ie. > Can Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector > configurable in Solr 5.5.3 too?? > > https://issues.apache.org/jira/browse/SOLR-5730 > > The

Re: Arabic words search in solr

Hi Mohan, When I said "the ICU folding filter should be the last filter, to allow the Arabic normalization and stemming filters to see the original words”, I meant that no filter should follow it. You did not make that change. Here’s what I mean:

Re: Indexing of documents in more than one step (SOLRJ)

Which version of Solr do you use? Is it always the same field? Again, without checking anything, see if it could be that field is not multivalue and your value is. In any case, this is inefficient way of indexing. If possible, stream both sources ordered by ID and merge them in one input doc

Re: SSL using signed client certificate not working

It sounds like Edge, Firefox, and Chrome aren't setup on your computer to do client authentication. You can set need client authentication to false and use want client authentication in solr.in.sh. This will allow browsers that don't present a client certificate to work. Otherwise you need to

Re: Indexing of documents in more than one step (SOLRJ)

No, it's not the case. In both steps I'm indexing documents from the same set of IDs (I mean the values of the 'id'). Maciej W dniu 15.02.2017 o 11:07, Emir Arnautovic pisze: I did not have time to test it or look at the code, but can you check if it could be the case when there is no

Core replication, Slave not flipping to master

Hello, Solr 5.4.1, multiple cores with two cores per shard. Zookeeper 3.4.6 (5 zookeeper ensemble). I have noticed an error with the replication between two cores in a shard. I’m having to perform a schema update which means I have to stop and start the cores. I’m trying to do this in a

SSL using signed client certificate not working

Hi, I have some problems with client certificates. By the look of it, it works with curl and safari prompts for and accepts my certificate. Does not work with Edge, Firefox or Chrome. The certificates are requested from our CA. When requesting https://s02/solr in the browser, it doesn't prompt

Re: Continual garbage collection loop

Thanks all who replied, lots of information to help us improve our use and management of Solr! > > On 15 February 2017 at 08:04 Michael Kuhlmann wrote: > > > The number of cores is not *that much* important compared to the index > size, but each core has its memory

Re: Indexing of documents in more than one step (SOLRJ)

I did not have time to test it or look at the code, but can you check if it could be the case when there is no document with a, b, c fields and you are trying to update it with d, e, f using partial update syntax. Emir On 15.02.2017 09:25, Maciej Ł. PCSS wrote: Dear All, how should I handle

Re: Can SOLR-5730 patch be backported to Solr 5.5.3

Can the Solr branch_5x (specifically, browsing the repo at the point of SOLR-5730's last commit) be a good place to check in regards to this task? The team is upgrading to Solr 5 from Solr 4 for now. Im an intern and had been asked to implement these features and discovered that they already

Re: Can SOLR-5730 patch be backported to Solr 5.5.3

The other question is what do you hope to gain from SortingMergePolicy and EarlyTerminatingSortingCollector, and why would you want to do that in Solr 5.5.3 and not upgrade to Solr 6? What prevents you from upgrading I guess is my real question? On 15 February 2017 at 05:06, Erick Erickson

Indexing of documents in more than one step (SOLRJ)

Dear All, how should I handle the following scenario using SOLRJ? Index a collection of documents (fill fields a, b, c). Then index the same collection but this time fill fields d, e, f. In a pseudo-code it would be: step1(collectionX); step2(collectionX); solrCommit(); See my

Re: Continual garbage collection loop

The number of cores is not *that much* important compared to the index size, but each core has its memory overhead. For instance, caches are based on cores, so you're having 36 individual caches per type. Best, Michael Am 14.02.2017 um 16:39 schrieb Leon STRINGER: >> On 14 February 2017 at