Thanks Kevin. I'll move the discussion to dev mailing list
On Wed, Apr 2, 2025, 4:18 PM Kevin Liang (BLOOMBERG/ 919 3RD A) <
klian...@bloomberg.net> wrote:
> I don't have enough knowledge to give the greenlight on this, but on a
> high level it seems reasonable. This question is probably more app
First thought, off the top of my head : does the process running the Solr
restore have permission / visibility to the new S3 location?
(If I'm understanding you correctly ...) The Solr backup process clearly had
permission to the old location; and you can see the new location with an admin
us
: So, I tried a cursor-based approach, sorting on two fields, the non-unique
: one which I want to have the result sorted on, plus the unique id field.
: However, the sorting is done on the result of each query, not on the
: complete data set.
You need to elaborate on what you mean by this and h
: Additionally to the copy field, I need to add the destination field (in
: the JSON API, with "add-field") to not give it its default attribute
: values.
:
: I wonder why it is working for another schema without doing so, but
: nevertheless, it's working now.
Because...
: On the developmen
You may try to experiment with query time {!join mode=score max} to join
from prods to supplier.
Query time reduces supplier reindex burden.
And you'll get a scored and cropped page of suppliers, but completely lost
product hits.
Then you can search for products by supplier again in [subquery] resu
Hi all,
In our index, we have data of suppliers along with their products which we
display on front-end, wrt search requests.
*Example:For a supplier with id: 678, we have 2 products in our index*
*product-id(unique)*
*document1:*
{
product-id: 123
product-price: 2000rs
product-name: Jute bags
Hello,
I think we might need some more context here, that is to say, why are you
using Solr 5.5.1? That was released in 2016 and is very much out of date
and unsupported (and will contain a number of critical CVEs).
So rather than trying to make it work, can you instead move to the latest
release
Answering myself:
Additionally to the copy field, I need to add the destination field (in the
JSON API, with "add-field") to not give it its default attribute values.
I wonder why it is working for another schema without doing so, but
nevertheless, it's working now.
kr,
Mag.phil. Robert Ehren
