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

Cassandra Targett closed SOLR-4433.
-----------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 6.0)
                       (was: 4.9)

We now (Solr 5+) ask users just getting started with SolrCloud to use the 
bin/solr script and the cloud example. That loads a config from a configset 
template and takes care of the problem described in this issue.

> Developer Curb Appeal: automatically cleanup, or at least offer to cleanup, 
> any docs from template index directory
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4433
>                 URL: https://issues.apache.org/jira/browse/SOLR-4433
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>    Affects Versions: 4.1
>            Reporter: Mark Bennett
>
> When setting up SolrCloud, we have the admin make a copy of example directory 
> into the shard template.
> But we issue the warning "Make sure there are no documents present"
> Doc reference:
> http://lucidworks.lucidimagination.com/display/solr/Getting+Started+with+SolrCloud
> Red box: "...  On the other hand, make sure also that there are no documents 
> in the example directory before making copies."
> We don't say what happens if the data directory is not empty?  If this is 
> really bad, then I'm not sure if we should just automatically nuke it, or 
> prompt them, or give a warning and exit, or maybe a command line switch, OR 
> maybe just move it out of the way, maybe renaming it to something with a 
> ".NON-CLOUD-INDEX".
> There should be an opportunity to do this.  When SolrCloud initializes a new 
> shard node, I believe it knows that this is the first time (based on whether 
> ZooKeeper has persisted this node's shard assignment, etc.)



--
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

Reply via email to