[ https://issues.apache.org/jira/browse/SOLR-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-6778: --------------------------- Priority: Blocker (was: Critical) +1 to your patch tim ... we can always iterate more, but at a minimum some sort of change like this has to make it into 5.0 to be viable for new users. > Dead end UX when following README > --------------------------------- > > Key: SOLR-6778 > URL: https://issues.apache.org/jira/browse/SOLR-6778 > Project: Solr > Issue Type: Improvement > Components: documentation > Affects Versions: 5.0 > Reporter: Alexandre Rafalovitch > Priority: Blocker > Labels: documentation, examples, usability > Fix For: 5.0 > > Attachments: SOLR-6778.patch > > > After 'downloading' (building) Solr 5 distribution, the README says: > {quote} > To start Solr for the first time after installation, simply do: > bin/solr start -f > {quote} > That will bring Solr server up, but there is no longer a *collection1*, so we > get *no cores* message, clicking on which brings up an "Add new core" > dialogue. > Which - of course - does not actually allow us to create a new core but will > just complain bitterly that one does not exist on the file system. And the > server will throw a scary stack exception. > We have a catch-22 here. So, either the README needs to go into *run an > example* sequence or ??? -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org