KhushJain opened a new pull request, #4218: URL: https://github.com/apache/solr/pull/4218
https://issues.apache.org/jira/browse/SOLR-17973 <!-- _(If you are a project committer then you may remove some/all of the following template.)_ Before creating a pull request, please file an issue in the ASF Jira system for Solr: * https://issues.apache.org/jira/projects/SOLR For something minor (i.e. that wouldn't be worth putting in release notes), you can skip JIRA. To create a Jira issue, you will need to create an account there first. The title of the PR should reference the Jira issue number in the form: * SOLR-####: <short description of problem or changes> SOLR must be fully capitalized. A short description helps people scanning pull requests for items they can work on. Properly referencing the issue in the title ensures that Jira is correctly updated with code review comments and commits. --> # Description When a cross-collection join query is executed with `shards.preference` (e.g., `replica.leader:false`), the preference is silently ignored. The join's internal `/export` stream to the "from" collection picks replicas arbitrarily, disregarding any replica routing preferences. # Solution This is a two-part problem: 1. `CrossCollectionJoinQParser` only iterates over `localParams` (the `{!join ...}` syntax), so request-level `shards.preference` is never captured. 2. `CrossCollectionJoinQuery.createCloudSolrStream()` creates a `StreamContext` without setting request params or a `RequestReplicaListTransformerGenerator`, so even if the parameter were present, the stream has no node context to evaluate preference rules. # Tests Added 4 new tests in `CrossCollectionJoinQueryTest`: - `testShardsPreferenceRequestParamPropagation`: verifies request-level `shards.preference` is propagated into the query's `otherParams` - `testShardsPreferenceLocalParamTakesPrecedence`: verifies `localParams` value takes precedence over request-level param - `testShardsPreferenceWithCrossCollectionJoin`: end-to-end test using per-node `/export` metrics to confirm `replica.leader:true` and `replica.leader:false` route to the correct replica - `testShardsPreferenceLocationLocal`: end-to-end test verifying `replica.location:local` routes the `/export` stream to the co-located replica # Checklist Please review the following and check all that apply: - [x] I have reviewed the guidelines for [How to Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my code conforms to the standards described there to the best of my ability. - [x] I have created a Jira issue and added the issue ID to my pull request title. - [x] I have given Solr maintainers [access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation) - [x] I have developed this patch against the `main` branch. - [x] I have run `./gradlew check`. - [x] I have added tests for my changes. - [ ] I have added documentation for the [Reference Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide) - [x] I have added a [changelog entry](https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc) for my change -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
