Based on the problem description, it seems you might have a work-around of
submitting collection admin commands to the Overseer node instead? At
least during the upgrade.
Also... I wonder if upgrading to 9.0 instead of 9.6 may help. Not that I
know of anything specific that's incompatible but I c
No, but I want to say that's so weird. I think it's ultimately a JTS issue
and mybe a Spatial4j issue and not a Solr issue. You might try the
latest JTS. You could work around the problem by basically doing a
disjunction (OR) across multiple spatial query clauses, all in one FQ.
Something li
Hi all,
I am getting:
{
"responseHeader": {
"status": 400,
"QTime": 62,
"params": {
"q": "*:*",
"fq": "{!field f=geo_rpt
v='Intersects(MULTIPOLYGON(((13.272047419856218
48.20342387325925,13.370237727473405
48.244137723977545,13.44302215130153
48.17504227627839,13.3839706
I followed the instructions from
https://solr.apache.org/guide/solr/latest/indexing-guide/indexing-with-tika.html
with the techproducts example and I was able to reproduce the 500 file
permission error.
However, changing the line had no effect (restarted and rebuilt the project
and instance as wel
