Issue with indexing document - solr 7.5

2019-06-14 Thread Rohan Kasat
Hi All, Am indexing json documents with parent child relationship's and have the following schema on Solr 7.5 id Document - { "id": "Year-2019", "year": 2019, "_childDocuments_": [ { "id": "5-2019", "month": 5 } ] } and the error am getting

Re: Facet on multicore search when one field exists only in one of cores

2019-06-14 Thread Claudio R
Hi Shawn,Thank you very much for your quick answer.The use of dynamic field "ignored" works, but it does not seem to be the correct way to solve the problem.We will try to equalize the cores. Em sexta-feira, 14 de junho de 2019 11:18:40 BRT, Shawn Heisey escreveu: On 6/14/2019 7:54

Re: Facing issue ith MinMaxNormalizer

2019-06-14 Thread Kamal Kishore Aggarwal
Hi Christine, Thanks for the reply. I had identified the same issue. So, applied the below fix in the custom jar. this.max = Float.parseFloat(max.replace("\"", "")); this.min = Float.parseFloat(min.replace("\"", "")); And, it worked. Thanks for confirming that this is an issue in solr 6.6.2

Re: Facet on multicore search when one field exists only in one of cores

2019-06-14 Thread Shawn Heisey
On 6/14/2019 7:54 AM, Claudio R wrote: When I try this request to get facet of fields: fieldA, fieldB and fieldC on multicore search, I get error: http://localhost:8983/solr/core1/select?q=*:*=localhost:8983/solr/core1,localhost:8983/solr/core2=*,[shard]=true=fieldA=fieldB=fieldC Error from

Facet on multicore search when one field exists only in one of cores

2019-06-14 Thread Claudio R
Hi, I am using Solr 6.6.0 in mode standalone with 2 cores. The first core has the schema: id fieldA fieldB The second core has the schema: id fieldA fieldC When I try this request to get facet of fields: fieldA, fieldB and fieldC on multicore search, I get error:

Solr Sudden I/O spike

2019-06-14 Thread Sripra deep
Hi, Any help would be appreciated, I am using solr 7.1.0, Suddenly we got a high I/O even with a very low request rate and the core went down. Did anybody experience the same or root cause of this. Below are the log error msg that we got from solr.log 2019-06-06 10:37:14.490 INFO

Re: SOLR JOIN

2019-06-14 Thread Paresh
They are logically different that is why kept in different collections. Collection1: The purpose is to do Global Text Search for all objects through multiple document types Collection3: The purpose is to have search for some other type of objects whose documents are in Millions and takes GBs size.

Re:Facing issue ith MinMaxNormalizer

2019-06-14 Thread Christine Poerschke (BLOOMBERG/ LONDON)
Hello Kamal Kishore, Thanks for including the Solr version alongside your question! What you describe sounds like the https://issues.apache.org/jira/browse/SOLR-11163 issue which is fixed in 7.0.0 but not 6.6.2 release. The fix is a simple two line change to MinMaxNormalizer and perhaps one

Re: SOLR JOIN

2019-06-14 Thread Jörn Franke
Put them in one collection > Am 14.06.2019 um 07:17 schrieb Paresh : > > I am actually able to make this work by doing multiple JOINs - > 1. Do query on Collection1 > 2. JOIN with Collection3 (document type1 field) > 3. JOIN with Collection3 (document type2 field) > 4. Do not fetch any data

Re: SOLR JOIN

2019-06-14 Thread Paresh
I am actually able to make this work by doing multiple JOINs - 1. Do query on Collection1 2. JOIN with Collection3 (document type1 field) 3. JOIN with Collection3 (document type2 field) 4. Do not fetch any data except faceting information But the other problem is, it is very slow. Are there any