[ 
https://issues.apache.org/jira/browse/SOLR-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-9308:
---------------------------
    Attachment: SOLR-9308.patch

Suggested patch:

* refactors some redundant ShardRequest init logic into a new helper method
* updates the ShardRequest init logic to copy the params from the original 
request, explicitly removing a few we definitely don't want before adding the 
new (shard specific) "ids" param.
* updates tests to use filter queries in some RTG requests, against both 
committed & uncommitted docs
* ensures that the filter Query objects are rewritten before trying to call 
createWeight on them (unrelated bug that seems like it would also affect some 
single node RTG requests depending on the type of fq used ... discovered during 
testing)

This fix also seems to resolve all of the issues noted in SOLR-9286 (which 
makes sense: since no params were being copied for the shard requests, any 
non-default fl transformers would never be generated by the shards).  So this 
patch also enables all of the test logic that was blocked on SOLR-9286.

[[email protected]] - what do you think?

> SolrCloud RTG w/fq seems to ignore fqs - regardless of wether docs are 
> committed or not
> ---------------------------------------------------------------------------------------
>
>                 Key: SOLR-9308
>                 URL: https://issues.apache.org/jira/browse/SOLR-9308
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>         Attachments: SOLR-9308.patch
>
>
> While working on a robust randomized test for SOLR-9285, I can't seem to get 
> filter queries on RTG to work at all -- even when the docs are fully 
> committed.
> steps to reproduce to follow in comment...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to