[ 
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227012#comment-14227012
 ] 

Alexandre Rafalovitch commented on SOLR-3619:
---------------------------------------------

Why can't we have 
{quote}
/server
/logs
/homes (whatever name, if not examples)
/homes/default
/homes/cloud
/exampledocs
{quote}

Then, the /server is immutable, can be copied around and so on. And the users 
do not have to grep the file system to look for where the files changed.

The problem is not when the user creates something (though you bet they will 
freak out over the error message). The problem is when they come back the next 
day and something goes wrong. And they have to figure out what happened behind 
the scenes. Or when they want to delete the examples they created all over the 
place and want to start a fresh setup of their own. 

At the moment, if they create schemaless and techproducts, they go together in 
a very deep directory under server. If they create cloud example, we get two 
directory copies (with logs, not just those examples I complained about) in a 
random (current directory) location. 

Another way to look at it is _what do I need to delete to get back to the 
original setup_. At the moment, it's something in /bin (pid files), something - 
not everything - in some deep directories (/server/solr/X,Y,Z), something else 
in another deep directory (/server/logs) and something in whatever location I 
was in when I run cloud example. Even I just delete the whole setup and just 
untar the build archive.

> Rename 'example' dir to 'server' and pull examples into an 'examples' 
> directory
> -------------------------------------------------------------------------------
>
>                 Key: SOLR-3619
>                 URL: https://issues.apache.org/jira/browse/SOLR-3619
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Timothy Potter
>             Fix For: 5.0, Trunk
>
>         Attachments: SOLR-3619.patch, SOLR-3619.patch, SOLR-3619.patch, 
> managed-schema, server-name-layout.png, solrconfig.xml
>
>




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