[
https://issues.apache.org/jira/browse/SOLR-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727053#comment-13727053
]
Mark Miller commented on SOLR-5104:
-----------------------------------
We certainly want to do this, and I don't consider it removing a feature. It's
purely an improvement IMO. The main reason I have not pushed for it yet was
that the it killed the admin UI - but now that that is fixed, this is the next
step.
This is a relic from the pre multi core days - when Solr was one index and that
is it. Backcompat sludge is what has kept it around IMO - we want to act like
most systems and start empty. It should be very simple for a user to create his
first collection, but he should be the one to name it. As Grant mentions, this
is certainly what you want for scriptibility, and it's more consistent with
other systems for users as well.
A new user should:
1. Start Solr
2. Name and create their first collection.
When they want more collections, repeat step 2, a step they learned right away.
> 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]
