Can you solve this problem by adding all documents into the same collection
and performing self joins. You could add a field called rec_type to
differentiate between the records.
There are two good reasons for wanting to do this.
1) This allows you to route by the join key and easily co-locate re
Hey Lulu,
While this is not a Solr specific issue I suspect your server is not configured
to accept connections over older TLS/SSL versions but without seeing the
handshake it can only be an assumption. So in this instance setting your
client to handshake over TLS 1.1 is not going to fix your
Thanks Joel!
On my list is to investigate Block Joins and Nested Child docs.
https://solr.apache.org/guide/8_8/other-parsers.html#block-join-query-parsers
https://solr.apache.org/guide/8_8/indexing-nested-documents.html#indexing-nested-documents
However, it looks like you are not suggesting usi
Block join is another option. If that works for you, from an indexing
standpoint, it's the most performant query time join.
If block indexing doesn't work for you then the optimized self join is
almost as fast.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Jul 9, 2021 at 11:31 AM Matt K
WIth the Solr operator I see there is an updateStrategy for the managed
Solr upgrades. But I don't see anything mentioned about pod disruption
budgets. I saw that a Zookeeper pod disruption budget is installed with the
Zookeeper that deploys with the Solr operator but I didn't see one for Solr.
Do
Unfortunately the podDisruptionBudget isn't so useful for Solr applications.
If we are merely talking about doing restarts of the Pod Spec (which could
include the OS that the Solr image uses), then the
updateStrategy takes care of that very well. If you are talking about doing
upgrades of the Kub
Thanks Houston, that answers my question perfectly.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Jul 9, 2021 at 12:02 PM Houston Putman
wrote:
> Unfortunately the podDisruptionBudget isn't so useful for Solr
> applications.
>
> If we are merely talking about doing restarts of the Po
Using debug=all you can review in what field(s) the match was on. That
should give clues.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Wed, Jul 7, 2021 at 3:23 PM Flowerday, Matthew J <
matthew.flower...@gb.unisys.com> wrote:
> Hi There
>
>
>
>
