You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cassandra Targett (JIRA)" <ji...@apache.org> on 2016/11/18 18:28:59 UTC

[jira] [Closed] (SOLR-4902) Confusing names/identifiers in example schema

     [ https://issues.apache.org/jira/browse/SOLR-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassandra Targett closed SOLR-4902.
-----------------------------------
    Resolution: Won't Fix

Closing this older issue.

The new Admin UI puts a better focus on collections so they are more straightforward to work with. In addition, collection1 is gone, so that confusion is removed.

There is still a catchall field that's now called {{_text_}} (from the data_driven_schema, might be different in other examples), which is either more or less confusing depending on how you look at it. However, it's not hard to figure out from the Admin UI that the field is populated by data in all the other fields ("Copied from *") and that feels all right to me since I haven't heard this complaint widely.

If folks disagree and think this should be open still, please feel free to reopen.

> Confusing names/identifiers in example schema
> ---------------------------------------------
>
>                 Key: SOLR-4902
>                 URL: https://issues.apache.org/jira/browse/SOLR-4902
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Shawn Heisey
>            Priority: Minor
>
> The following came up in the IRC channel today:
> {noformat}
> 16:34 < sayuke> I can't work this out for the life of me. Is text in text:blah
>                 some sort of special syntax for searching all text fields?
>                 Google keywords other than text: appreciated
> {noformat}
> A better name for this would be something that includes catchall.  There is a lot of documentation that mentions this field name that would all have to be updated.
> Another new user was well-confused by the Admin UI with SolrCloud, expecting that they would see the collections that they have created, instead of the weird shardN_replicaN cores they found.  This problem is further compounded by the fact that the default core in the example is named 'collection1' although it is not in fact a collection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org