6d71a0aced
* Creating Scripting contrib module to centralize the less secure code related to scripts. * tweak the changelog and update notice to explain why the name changed and the security posture thinking * the test script happens to be a currency.xml, which made me think we were doing something specific to currency types, but instead any xml formatted file will suffice for the test. * Update solr/contrib/scripting/src/java/org/apache/solr/scripting/update/ScriptUpdateProcessorFactory.java * Update solr/contrib/scripting/src/java/org/apache/solr/scripting/update/package-info.java * drop the ing, and be more specific on the name of the ref guide page * comment out the script update chain. The sample techproducts configSet is used by many of the solr unit tests, and by default doesn't have access to the jar file in the contrib module. This is commented out, similar to how the lang contrib is. * using a Mock for the script processor in order to keep the trusted configSets tests all together. * tweak since we are using a mock script processor Co-authored-by: David Smiley <dsmiley@apache.org>
Default Solr Home Directory
This directory is the default Solr home directory which holds configuration files and Solr indexes (called cores).
Basic Directory Structure
The Solr Home directory typically contains the following...
solr.xml
This is the primary configuration file Solr looks for when starting; it specifies high-level configuration options that apply to all of your Solr cores, such as cluster-wide SolrCloud settings like the ZooKeeper client timeout.
In addition, you can also declare Solr cores in this file, however it is recommended to just use automatic core discovery instead of listing cores in solr.xml.
If no solr.xml file is found, then Solr assumes that there should be a single SolrCore named "collection1" and that the "Instance Directory" for collection1 should be the same as the Solr Home Directory.
For more information about solr.xml, please see: https://lucene.apache.org/solr/guide/solr-cores-and-solr-xml.html
Individual SolrCore Instance Directories
Although solr.xml can be configured to look for SolrCore Instance Directories in any path, simple sub-directories of the Solr Home Dir using relative paths are common for many installations.
Core Discovery
During startup, Solr will scan sub-directories of Solr home looking for a specific file named core.properties. If core.properties is found in a sub-directory (at any depth), Solr will initialize a core using the properties defined in core.properties. For an example of core.properties, please see:
example/solr/collection1/core.properties
For more information about core discovery, please see:
https://lucene.apache.org/solr/guide/defining-core-properties.html
A Shared 'lib' Directory
Although solr.xml can be configured with an optional "sharedLib" attribute that can point to any path, it is common to use a "./lib" sub-directory of the Solr Home Directory.
ZooKeeper Files
When using SolrCloud using the embedded ZooKeeper option for Solr, it is common to have a "zoo.cfg" file and "zoo_data" directories in the Solr Home Directory. Please see the SolrCloud documentation for more details.