Question for ExpandComponent

Hi – I am working with the CollapsingQParserPlugin and want to combine it with the ExpandComponent as documented in the reference manual (https://solr.apache.org/guide/solr/latest/query-guide/collapse-and-expand-results.html#expand-component). I wanted to ask if it possible to control the fields

Possible issue with nesting and the pf parameter

ot;scherfig parent which doc_type:work v pid.material_type\") ``` which worries me slightly. It looks like "parent which" is part of what solr is looking for in the work.creator field? The "interesting" bit is that, if I remove the line with `"pf":"work.creator"`, then that part of the debug output is no longer there. Is there an issue with `pf` here? Or am I formatting my query wrongly? Thanks in advance for any insight you can provide. Best regards, /Noah -- Noah Torp-Smith (n...@dbc.dk)

Facet counts for first N hits

/getting-facet-counts-for-10-000-most-relevant-hits#selection:3.655.119), but the links there are not working any longer. I guess I could fetch the 1000 documents and extract the documents on the client side, but I'd avoid that if solr could do it for me. Thanks, /Noah -- Noah Torp-Smi

using childFilter to restrict "child" docs by "grandchild" information

ation stored at the third level. I am not sure how to do that. Can anyone help? Thanks a lot in advance, and best regards. /Noah -- Noah Torp-Smith (n...@dbc.dk)

Sv: using childFilter to restrict "child" docs by "grandchild" information

. Specifying an instance-level restriction seems to make all the pid-level documents vanish. Thanks, /Noah -- Noah Torp-Smith (n...@dbc.dk) Fra: Mikhail Khludnev Sendt: 29. juni 2022 08:32 Til: users@solr.apache.org Emne: Re: using childFilter to restrict

Sv: using childFilter to restrict "child" docs by "grandchild" information

Interestingly, I found that [child childFilter=$pidfilter limit=-1]&pidfilter=+instance.agency:94 also worked - I get the pid that is present at that library. It's when I restrict at both pid and instance level it does not seem to work. -- Noah Torp-Smith (n.

Ranking based on number of OR clauses matched

are returned by solr would require changes we would like to avoid if possible. I realize this might be a "classical" question but I have not been able to formulate a query in google/stackexchange that gave me an answer. Thanks! /Noah -- Noah Torp-Smith (n...@dbc.dk)

Sv: Ranking based on number of OR clauses matched

riments to verify) take priority over how many OR clauses from one of the fqs that are matched. That makes sense, but I wonder if there is a way to work around that? -- Noah Torp-Smith (n...@dbc.dk) Fra: Alessandro Benedetti Sendt: 26. august 2022 11:26

Sv: Ranking based on number of OR clauses matched

;uddøde dyr\" \"forhistoriske dyr\")", "filter": [ "doc_type:work" ], "fields": "work.workid work.title work.creator work.subject_dbc score", "offset": 0, "limit": 100, "params"

Sv: Ranking based on number of OR clauses matched

I was simply trying to convey the simplest possible example that shows the issue. The real query is more complicated than that. Anyway, I think the point about `fq` not influencing the score explains it. Thanks for the help. -- Noah Torp-Smith (n...@dbc.dk

Slowness when searching in child documents.

r-denormalizing-solr-data.html) and it helps when doing it for a few child fields. But as said, there are more properties in the real model than those I have mentioned here, so that also involves some complications. Kind regards, /Noah -- Noah Torp-Smith (n...@dbc.dk)

Sv: Slowness when searching in child documents.

t;: 5, "ps3": 5 } } This fetches 21 workids and it takes more than 20 seconds. If I remove the first part of the filter (the one with parent which), it fetches 33 workids in less than 200 miliseconds. I does not matter if I do it with or without the filtering to materi

Sv: Slowness when searching in child documents.

olr source code)? Best regards, /Noah -- Noah Torp-Smith (n...@dbc.dk) Fra: Mikhail Khludnev Sendt: 3. januar 2023 19:29 Til: users@solr.apache.org Emne: Re: Slowness when searching in child documents. Hold on. > I remove the first part of the filter

issue with f..qf in solr 9.4

same to the /query endpoint in 9.4, I get a message stating that the "all" field does not exist. We use the f.<>.qf construction for a variety of things, so it'd be sad for us if that was discontinued. Is this a bug or intentional? Thanks, /Noah -- Noah Torp-Smith (n...@dbc.dk)

Sv: issue with f..qf in solr 9.4

Just for clarification: this works in 9.3 (like 9.1.1), and not 9.4. Thanks for reacting to this, I appreciate it. I'll keep an eye on SOLR-16916. Regards, /Noah -- Noah Torp-Smith (n...@dbc.dk) Fra: Chris Hostetter Sendt: 24. oktober 2023 19:32 Til:

Sv: issue with f..qf in solr 9.4

I have just tried this with 9.4.1, and I can confirm that it works as intended. Thanks for fixing, much appreciated! Best regards, /Noah -- Noah Torp-Smith (n...@dbc.dk) Fra: Noah Torp-Smith Sendt: 25. oktober 2023 09:59 Til: users@solr.apache.org Emne: Sv

Solr in write-only mode?

Hello, We have a setup where we periodically index a solr “offline” and then copy the data folder to a storage location. When we then deploy our solrs to production, the containers then download that data folder to the right place in the file system before the solr server is started. After the