[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414142#comment-13414142
]
Jan Høydahl commented on SOLR-3619:
-----------------------------------
The name "server" is good in that it indicate that there's actually an
appserver inside.
But it feels wrong to include one example config in "server" and leave the
others by themselves. After all, the nature of a search engine is that every
user needs their own custom schema, so anything we provide OOTB will per
definition be an example. We should not fool people into thinking that there is
a "default" or "generic" schema - we simply provide a starting point. So to
make it even easier for beginners to explore all of Solr including DIH and
extracting-handler etc, let's have simply *one* examples/solrhome with all the
examples we wish to expose (and maintain!). It will give them more prime-time,
we can get rid of the old "multicore" etc.
Seen together with the start-scripts issue, I say we should have a top-level
{{solr/bin}} with all the scripts, including zkcli, and a {{feed-example}}
script. Here's my take on new structure:
{noformat}
├── bin
│ ├── feed-example.sh
│ ├── start-server.sh
│ ├── stop-server.sh
│ ├── zkcli.bat
│ └── zkcli.sh
├── contrib
├── dist
├── docs
├── examples
│ ├── exampledocs
│ │ ├── docs
│ │ └── products
│ └── solrhome
│ ├── DIH-db
│ ├── DIH-rss
│ ├── docs
│ ├── products
│ └── solr.xml
└── server
├── solr.home (file)
└── webapps
{noformat}
With this setup, the {{products}} core would be today's "collection1", and
{{docs}} would be a handful of PDFs and HTMLs for use with solr-cell and/or DIH
files example. Today's "collection1" is not very well tuned for PDF/HTML kind
of docs, so it may be better with a dedicated schema for such docs.
The one-liner for starting and feeding examples could then be something like:
{noformat}
cd solr/bin; ./start-server.sh; ./feed-example.sh all
{noformat}
But if the example configs are not below {{server/}} anymore, the old {{cd
server; java -jar start.jar}} will not work anymore. Soft-linking a "solr"
folder to {{../examples/solrhome}} wouldn't work for Windows, so a nice
solution could be to in addition to looking for a {{./solr}} folder for our
SOLR_HOME, we look for a {{./solr.home}} file with one line poining to
SOLR_HOME. Separating binaries and data this way is also a preferred way for
many, and it makes the whole concept of SOLR_HOME more clear to people - today
some are confused about {{solr/example/solr}} being SOLR_HOME.
> Rename 'example' dir to 'server'
> --------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3619.patch, server-name-layout.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
