Hi, I need to move an existing solr instance to kubernetes.
I am trying to write a Dockerfile to
1. create a core
2. load data
3. run solr
I am able to create a core from my existing config and run it with
"docker run -v myconf:/myservice solr:6.6 -c myservice -d /myservice"
But i want to avoid
Hi Bjørn,
First the Dockerfile is simply a blue-print to create an image.
So you wouldn’t run the Solr directly from the Dockerfile.
1. Instead you would create your custom image with the following content:
FROM solr:6.6
ADD
2. To build the image you can use the following command:
docker
So do you want to pacakge a pre-built index into a docker image and distribute
that image to k8s? Or do you also need to index data to Solr live in k8s?
For the first case, where you periodically re-build an index and includes it in
the image, Timo's Dockerfile inheritance could work well. Benef
Hi,
It appears this was broken in 8.0 by
https://issues.apache.org/jira/browse/SOLR-12768
And then fixed in 9.0 (not released) by SOLR-15156
I didn't back-port the fix because I thought users might be relying on the
escaping behavior. I didn't realize such escaping didn't exist before
SOLR-12768
The Solr PMC is pleased to announce the release of the Apache Solr Operator
v0.3.0.
The Apache Solr Operator is a safe and easy way of managing a Solr
ecosystem in Kubernetes.
This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The relea
I need to disable Config API on my SOLR, where the system is already installed
and running.
As its mentioned over web, I need to add the string:
SOLR_OPTS="$SOLR_OPTS -Ddisable.configEdit=true"
to the solr.in.sh file. However, I dont have the solr.in.sh file.
I also found that another way is to s
-Ddisable.configEdit=true does not work
Hello! I have a question about the text_en_splitting fieldType (solr 8.8.2,
very vanilla schema). I noticed that it was failing for queries like:
`title:"The
Mark of the Crown"`, but succeeding for queries like `title:The Mark of the
Crown`. Using the solr analysis tool, I noticed that the index an
Thanks David for confirming this and the work around, really appreciate it.
I also found a subquery could give correct results, though haven't tested
performance comparison with childFilter. I had never used subquery before
so it hadn't occurred to me. Will try them both out.
fq={!parent which='d
I'm reaching out to our user community to get opinions on what Solr should
do to be more secure-by-default.
TL;DR: Solr 9 has better secure-by-defaults, but maybe we should do more
like have Solr pick some of it's default settings dependent on a new
env=dev|prod.
I was shown a glimpse of a massiv
On Thu, May 6, 2021 at 5:25 PM David Smiley wrote:
>
> I'm reaching out to our user community to get opinions on what Solr should
> do to be more secure-by-default.
>
> TL;DR: Solr 9 has better secure-by-defaults, but maybe we should do more
> like have Solr pick some of it's default settings depe
Hello Solr user community,
**What sort of security problems warrant publishing a CVE?**
The Solr PMC grapples with this internally as we have access to messages
sent to secur...@solr.apache.org which report possible vulnerabilities /
security weaknesses in Solr. Some reporters pressure us to iss
I think that part of the challenge goes to the deeper issue that configuring
Solr isn’t easy. We don’t really have the concept of a environment specific
settings file. I’d love to see a -env=production.yml or -env=development.yml
type file that was the single place for all settings, and had sane
One problem I have seen in the past is cultural. Back when solr was mostly a
.war file it was very easy to say "secure your own tomcat" but in the era of
"solr is a database not a web app" it needs to embrace the entirety of that
distinction.
You can't have it both ways and I am not sure the c
14 matches
Mail list logo
