[
https://issues.apache.org/jira/browse/SOLR-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241658#comment-14241658
]
Alexandre Rafalovitch commented on SOLR-6833:
---------------------------------------------
Well, my proposal would be to have server directory locked down and everything
else being outside. Which I mentioned before in other JIRAs. I, unfortunately,
do not have that level of Solr contributor knowledge yet. Hopefully one day
soon, but for now most of my large contributions are outside of Solr codebase.
On the other hand, I am trying to understand what kind of things will be hard
to explain to the new users and - given their tendency to mess up - may cause
recovery or consistency issues. A QA-level contribution, you could say. And
that intuition comes from spending 3 years supporting multiple versions of
multi-million line Java code (BEA Weblogic back in the day) and seeing day
after day how even nearly-foolproof configurations do not survive new user's
eager attempts at making it work.
No offense is intended to anybody. I do realize it is a major layout
restructuring with the best intent. And it is great overall.
> bin/solr -e foo should not use server/solr as the SOLR_HOME
> -----------------------------------------------------------
>
> Key: SOLR-6833
> URL: https://issues.apache.org/jira/browse/SOLR-6833
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Timothy Potter
> Fix For: 5.0
>
>
> i think it's weird right now that running bin/solr with the "-e" (example)
> option causes it to create example solr instances inside the server directory.
> i think that's fine for running solr "normally" (ie: "start") but if you use
> "-e" that seems like the solr.solr.home for those example should instead be
> created under $SOLR_TIP/example.
> I would even go so far as to suggest that the *log* files created should live
> in that directory as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
