gerlowskija commented on PR #4110: URL: https://github.com/apache/solr/pull/4110#issuecomment-3862523347
Hmm...`HttpSolrCall` (where this path gets normalized) has a few codepaths that are dependent on `cores.isZooKeeperAware()` and are involved in path-setting. So I suspect the standalone code-paths just happen to avoid it? Or maybe there are URLs that would trigger the bug for standalone that we just didn't notice. Now, the deeper question of *why* HttpSolrCall should care whether we're in SolrCloud or not, I don't have a great answer for. I know Gus is setting out to disentangle a lot of this code, so maybe he has some context that's relevant here? -- 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]
