[
https://issues.apache.org/jira/browse/SOLR-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726503#comment-13726503
]
Grant Ingersoll commented on SOLR-5104:
---------------------------------------
My reason is b/c SolrDispatchFilter is filled with legacy cruft, this being one
of them. The simpler and more standard we can make all path handling, the
better. I don't really care much about shorter URLs and I don't buy the
prototyping/learning factor. In fact, I'd argue that it is harder b/c of it,
since you have a "magic" core and than all of your other cores. If you just
make the name of the collection part of the path always, there is no more
guessing.
The less legacy code for "plumbing" we carry forward in 5, the better off Solr
we will be.
And yes, I am working on making the possibility of a full blown REST API. See
SOLR-5091.
> Remove Default Core
> -------------------
>
> Key: SOLR-5104
> URL: https://issues.apache.org/jira/browse/SOLR-5104
> Project: Solr
> Issue Type: Sub-task
> Reporter: Grant Ingersoll
> Fix For: 5.0
>
>
> I see no reason to maintain the notion of a default Core/Collection. We can
> either default to Collection1, or just simply create a core on the fly based
> on the client's request. Thus, all APIs that are accessing a core would
> require the core to be in the address path.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
