lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Commented] (SOLR-4316) Admin UI - SolrCloud - extend core options to collections
Date Fri, 15 Feb 2013 17:05:13 GMT


Shawn Heisey commented on SOLR-4316:

bq. That's not right. You query the whole collection unless you pass the param distrib=false.

Very interesting!  That's not what I would have expected ... which IMHO violates the principle
of least surprise.  If the core has the same name as the collection, then it's not a violation
of that principle, and from what I understand, a 4.0.0 install *does* name the cores the same
as the collection.  I have not actually used 4.0.0 myself.

If cores are going to continue with the 4.1 method of having distinct names from the collection,
then I think a request to a core should not go cloud-wide unless you specifically request
that with an option.

Users who have never touched Solr before using SolrCloud of course have no expectations about
how things work, and probably will appreciate this behavior.  It would be a similar situation
for experienced users that have never tried the shards parameter.

Users like me that have distributed experience with older versions would be very surprised
by this behavior, and will be looking for a "collections" section in the admin UI -- which
is exactly what happened when I first started working with SolrCloud.

> Admin UI - SolrCloud - extend core options to collections
> ---------------------------------------------------------
>                 Key: SOLR-4316
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 4.1
>            Reporter: Shawn Heisey
>             Fix For: 4.2, 5.0
> There are a number of sections available when you are looking at a core in the UI - Ping,
Query, Schema, Config, Replication, Analysis, Schema Browser, Plugins / Stats, and Dataimport
are the ones that I can see.
> A list of collections should be available, with as many of those options that can apply
to a collection,  If options specific to collections/SolrCloud can be implemented, those should
be there too.

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