I just noticed that Solr no longer supports implicit collection name, at least for /update and /select. Is this an intentional feature deprecation, or just an outright bug? I hope it’s the latter, but with some of the drawn-out discussions related to core discovery and solr.xml in recent weeks, I’m just not sure.
For example, using the standard Solr example (ant run-example), I used to be able to say (still can in 4.3): curl “http://localhost:8983/solr/select/?q=*:*&indent=true” But with trunk and branch_4x this gives a 404 and I have to add the explicit collection name: curl “http://localhost:8983/solr/collection1/select/?q=*:*&indent=true” Ditto for /update. In 4.3 I can say: curl 'localhost:8983/solr/update?commit=true' -H 'Content-type:application/json' -d ' [{"id":"7cb8a43c","title":"My original Title", "content": "Initial content"}]' But with trunk and branch_4x this gives a 404 and I have to say: curl 'localhost:8983/solr/collection1/update?commit=true' -H 'Content-type:application/json' -d ' [{"id":"7cb8a43c","title":"My original Title", "content": "Initial content"}]' What’s going on? -- Jack Krupansky
