Hi,
We would like to extend SOLR default (named 'lucene' per:
https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html)
or eDisMax query parser with additional functionality of Lucene Span queries in
order to allow via standard parsers to execute position search (SpanFirst, etc.)
Hi,
Running Solr 7.7.2, cluster with 3 replicas
When CDCR is enabled, one of the target nodes gets an incorrect recovery
request.
Below is the content of the state.json file from the zookeeper.
"shards":{"shard1":{
"range":"8000-7fff",
"state":"active",
Hello,
I am trying to add a javaagent to monitor solr using a jmxtans agent. I am
using Solr version 7.7 and Java 8.
Basically I have added the following line at the end of my solr.in.sh:
SOLR_OPTS="$SOLR_OPTS
-javaagent:/path/jmxtrans-agent.jar=/path/jmxtrans-agent-config.xml"
After add that
Hello,
I am trying to add a javaagent to monitor solr using jmxtans agent. I am
using Solr version 7.7.
Basically I have added the following line at the end of my solr.in.sh
SOLR_OPTS="$SOLR_OPTS
-javaagent:/path/jmxtrans-agent.jar=/path/jmxtrans-agent-config.xml"
Solr startup correctly and it
here you go:
https://issues.apache.org/jira/browse/SOLR-14176
a detailed screenshot of the message can be made tomorrow, but it looks
pretty much to CSP to me - i have seen others with other applications using
CSP.
On Tue, Jan 7, 2020 at 6:45 PM Kevin Risden wrote:
> So this is caused by
Whenever I create a new collection on solr 7.7.2 cluster CDCR(uni
directional),
and once I disable buffer on both source and target nodes and start CDCR
process on the source node, then I encounter the error message "solr unable
to locate core..." on one of target node.
On source node, CDCR
So this is caused by SOLR-13982 [1] and specifically SOLR-13987 [2]. Can
you open a new Jira specifically for this? It would be great if you could
capture from Chrome Dev Tools (or Firefox) the error message around what
specifically CSP is complaining about.
The other thing to ensure is that you
Dear all,
I noted that in Solr Cloud 8.4.0 the graph is not shown due to
Content-Security-Policy. Apparently it violates unsafe-eval.
It is a minor UI thing, but should I create an issue to that one? Maybe it is
rather easy to avoid in the source code of the admin page?
Thank you.
Best
