coreRootDirectory!
If it takes a relative path, I am good with that. Great even.
We can update default solr.xml and fix documentation/whatever. The
rest of the files can go in solr.home.
Updated SIP-10 as primary path to explore for layout.
Regards,
Alex.
P.s. server/solr should be
On Fri, Sep 4, 2020 at 11:24 AM Alexandre Rafalovitch
wrote:
> > I really wish the default cores dir was not solr.home itself but one
> directory beneath.
> Why? That is worth exploring.
>
Because core discovery looks for cores in directories that are not cores
(e.g. filestore)
>
> I am ok -
> I really wish the default cores dir was not solr.home itself but one
> directory beneath.
Why? That is worth exploring.
I am ok - if others are - with solr.home containing
*) solr.in.sh
*) configset
*) logs
*) log and related configuration
*) userfiles
*) filestore
*) solr.xml
*) actual cores
On Fri, Sep 4, 2020 at 10:42 AM Alexandre Rafalovitch
wrote:
> I feel that maybe we don't treat it special mentally, but then it
> actually is. At least with minimum custom locations configured.
>
> Consider:
> 1) What is in "server", above "server/solr"
> * resources/log4j2.xml (because of
I feel that maybe we don't treat it special mentally, but then it
actually is. At least with minimum custom locations configured.
Consider:
1) What is in "server", above "server/solr"
* resources/log4j2.xml (because of magic jetty classpath mechanism)
* logs
* NOT server/solr/configsets (but
The parent directory of Solr home is not special. Where Solr Home is (as
you know) configurable. It's default location is different too, since it's
in /var/solr for both the Docker & service install script.
~ David Smiley
Apache Lucene/Solr Search Developer
Hello,
What do we call the directory above the solr.home?
E.g.
- "schemaless" in example/schemaless/solr/gettingstarted
- "node1" in example/cloud/node1/solr/gettingstarted_shard1_replica_n2
- "solr" in server/solr/book/conf
In solr.in.cmd we "may be" calling it "solr start dir"
In bin/solr, we
