[
https://issues.apache.org/jira/browse/SOLR-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678494#comment-13678494
]
Shawn Heisey commented on SOLR-4902:
------------------------------------
We might not end up implementing all my ideas, and that's OK. If all this
issue does is go through the config files and help us decide that what we have
now is good enough with a few documentation tweaks, then I think it has done
it's job.
> 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 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
