lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Commented] (SOLR-5104) Remove Default Core
Date Thu, 01 Aug 2013 14:57:48 GMT


Jack Krupansky commented on SOLR-5104:

bq. I see no reason to maintain the notion of a default Core/Collection.

Okay, here is the reason...

It is a great convenience and shortens URLs to make them more readable and easier to type.

It greatly facilitates prototyping and experimentation and learning of the basics of Solr.

And... compatibility with existing apps.

So, this notion that there isn't any "reason" is complete nonsense.

OTOH, maybe you are trying to suggest that there is some reason or valuable benefit to be
gained by requiring explicit collection/core name in the URL path. But, you have not done
so. Not a hint of any reason or benefit. So, if you do have a reason or perceived benefit
for eliminating a great convenience feature, please disclose it.

Or... is this not so much an issue of "reason" as because some code or tool change you are
contemplating does not support the kind of flexible URL syntax that Solr supports? Well, if
the benefits of the change in technology outweigh the loss of a valuable feature, then that
is worth considering, but as of this moment no positive tradeoff has been proposed or established.

OTOH, if there were a determined effort to give Solr a full-blown true REST API and THAT was
the motive for explicit collection name, I'd be 100% all for it.

Side note: Maybe "collection1" should become "example" to make it clear that real apps should
assign an app-meaningful name rather than leaving it as "collection1".

> Remove Default Core
> -------------------
>                 Key: SOLR-5104
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message