Hello All,
We are storing nested documents in Solr and when we query we would like to
get denormalized (flattened ) view of nested object. For ex
Stored Document :
1. {
2. course: "Java",
3. room: "10",
4. students: [
5. {
6. id: 12,
7. name: "Joe"
8. },{
9. id: 34,
Hi Phil.Staley
Thanks for your reply.
but I'm afraid that's a different problem.
Our problem can be confirmed since at least SOLR 7.3.0. (the oldest version we
have)
And we guess it might already exists since SOLR-9786.
https://github.com/apache/lucene-solr/commit/bf9db95f218f49bac8e7971eb953a9f
Hello, Community:
I have a question about interpreting a parsed query from Debug Query.
I used Solr 8.4.1 and LuceneQueryParser.
I was learning the behavior of ManagedSynonymFilter because I was curious
about how "ManagedSynonymGraphFilter" fails to generate a graph.
So, I try to interpret the par
Hi all,
A couple of months ago, I migrated my solr deployment off of some legacy
hardware (old spinning disks), and onto much newer hardware (SSD's, newer
processors). While I am seeing much improved search performance since this
move, I am also seeing intermittent indexing timeouts for 10-15 m
Apologies all I just realised I replied to the wrong thread. This is in
response to "Solr cloud on Docker?" not "SolrCloud" location for solr.xml".
Apologies for the confusion.
Thanks
Dwane
From: Dwane Hall
Sent: Monday, 2 March 2020 7:31 PM
To: Jan Høydahl ; s
Very low-tech and manual, but worth mentioning...
If there's a particularly large core that's doing a full recovery, and
you have access to the disk itself you can navigate to the relevant
directory for that core and run something like "watch -n 10 ls -lah"
or "watch -n 10 du -sh ." to see how the
: docid is the natural order of the posting lists, so there is no sorting
effort.
: I expect that means “don’t sort”.
basically yes, as documented in the comment right above hte lines of code
linked to.
: > So no one knows this then?
: > It seems like a good opportunity to get some performance!
I would use the Zookeeper and Solr images on the Docker Hub:
https://hub.docker.com/_/solr and https://hub.docker.com/_/zookeeper
Rob
> On 2 Mar 2020, at 11:46, Alvaro Lopez Medina wrote:
>
> Good morning,
>
> I am currently working on a demo to run a Solr cluster on Openshift (OCP).
> Curren
Hi,
I am working on improving the search app which is using 'qt' param heavily
to redirect requests to different handlers based on the parameters as
provided by the user.
Also for A B testing of different configurations, we have used qt param to
send request to different handlers.
My question her
I believe we are experiencing the same thing.
We recently upgraded to our Drupal 8 sites to SOLR 8.3.1. We are now getting
reports of certain patterns of search terms resulting in an error that reads,
“The website encountered an unexpected error. Please try again later.”
Below is a list of
Good morning,
I am currently working on a demo to run a Solr cluster on Openshift (OCP).
Currently, Openshift does not work with Helm out of the box and I would
like to know if there is any recommendation from the community to install
Solr on Openshift.
I have seen this repository (https://github
Hi,
Our team found a strange behavior of solr query parser.
In some specific cases, some conditional clauses on unindexed field will be
ignored.
for query like, q=A:1 OR B:1 OR A:2 OR B:2
if field B is not indexed(but docValues="true"), "B:1" will be lost.
but if you write query like, q=A:1 OR
Hey Jan,
Thanks for the info re swap there’s some interesting observations you’ve
mentioned below particularly the container swap by default. There was this
note on the Docker forum describing a similar situation you mention did you
attempt these settings with the same result?
(https://suc
13 matches
Mail list logo
