Hi all…. In working on SOLR-16800, which let’s us pass in a -solrUrl that is “http://localhost:8983 <http://localhost:8983/>” instead of the current “http://localhost:8983/solr”. This will set us up in the future when V2 api’s get called, and they are under “http://localhost:8983/api” ;-).
As part of that effort, I discovered that the “hostContext”, i.e the “/solr” bit of the URL can actually be changed! For example, “http://localhost:8983/uf” is a valid Solr URL. There is a bunch of plumbing around hostContext in our tests, including some randomization. See initHostContext and getHostContextSuitableForServletContext in BaseDistributedSearchTestCase for example. However, I am wondering if there is actually a valid use case for this? Especially since in the future, with our V2 api’s, they won’t be using this hostContext variability, they will always be under /api path. I’d like to rip out the ability to change the hostContext in 10.x (and if folks are up for it, back port to 9x) and establish that it’s always /solr for existing paths, and /api for the v2 API. Thoughts? Eric _______________________ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
