[
https://issues.apache.org/jira/browse/SOLR-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241533#comment-14241533
]
Hoss Man commented on SOLR-6833:
--------------------------------
bq. Should the distribution bundle include example/solr/solr.xml? Or should we
just copy server/solr/solr.xml to example/solr in the script if it's not there
already?
i think copying is the right way to go ... as far as the specific path...
i think a big question is if you intend/expect the different examples to
co-mingle. If i run "bin/solr -e techproducts" and then later i run "bin/solr
-e schemaless" is the expectation that i now have a single instance of solr
with *both* the techproducts and schemaless cores up and running in it? what
about example-DIH, which isn't a configset and already has it's own dir in
examples?
what about the cloud examples?
i think each "-e foo" option should create it's own "example/foo" directory (if
it doesn't already exist - DIH always will) and create a stub solr.xml there.
in the case of "-e cloud" it has to go one more level for each server:
"example/cloud/nodeN"
but the bottom line mantra should be: if it's created as part of an example, it
lives in example/
> 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]
