Hi,
I'm running into an exception with Solr 9.0.0 for a request that works fine
with Solr 8.11.2 and I have no idea why.
I've modified the techproducts example schema to store the _root_ field and
add a _nest_path_.
This request works fine with Solr 8.11.2, but not with Solr 9.0
Unfortunately I've witnessed the same issue. I think something in lucene
core is corrupted.
On Wed, Oct 19, 2022 at 5:00 PM Furkan Kalkan
wrote:
> Hi, we have a rare case of random mess up in parent-child document
> relations after patching all parent documents (including its child fields)
> in
Hi, Solr team
I am using Solr 8.11 to change join query to crossCollection join.
When I compared the query and result, I noticed something different.
If the join query is: q.op=AND&q=network_id:144750 AND {!join
fromIndex=company from=id to=advertiser_id v='name:(sky vip) AND
index_type:ADV'}
Whe
Hi, we have a rare case of random mess up in parent-child document
relations after patching all parent documents (including its child fields)
in Solr 8.11.1. Also, we realize that _root_:"" query returning
documents with different solr ids.
schema.xml: https://apaste.info/XU9z
example patch: https
Option one is also ideal for me
Le mardi 18 octobre 2022 à 18:27:35 UTC+2, Walton Goga
a écrit :
Option one is ideal for me
On Tue, 18 Oct 2022, 19:21 David Hastings,
wrote:
> I am definitely down for either option. I've been wanting to contribute
> for a while now
>
> On Tue, Oct
Hello,
The situation is not clear. Can you check the particular parsed query in
debugQuery=true output for both these cases?
If query is n't parsed as expected, cant' you make more explicit eg
name:(sky AND vip) AND index_type:ADV
or even
+name:(+sky +vip) +index_type:ADV
On Wed, Oct 19, 2022 at
Hi, Solr team
I am using Solr 8.11 to change join query to crossCollection join.
When I compare the query and result, I noticed something different.
If the join query is: q.op=AND&q=network_id:144750 AND {!join fromIndex=company
from=id to=advertiser_id v='name:(sky vip) AND index_type:ADV'}
W
Hi all,
Uwe (the project's JDK guru) has come up with a workaround that would enable
you to run with the official 9.0 image, given that the problem is isolated to
CaffeineCache:
Start Solr with flag
-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
See https
Yes, it is already being done:
https://issues.apache.org/jira/browse/SOLR-16464
Op wo 19 okt. 2022 om 05:51 schreef Bierenfeld Michael (BayWa
München-Zentrale) :
> Hi,
>
> solr uses this library in affected Versions. Are there any plans for
> Updates to apache-commons >= 1.10.0 ?
>
> Regards
>
>