lucene/solr/example
Jan Høydahl fa469cbbdb SOLR-3660: Velocity: Link to admin page broken
git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1364333 13f79535-47bb-0310-9956-ffa450edef68
2012-07-22 15:43:28 +00:00
..
cloud-scripts SOLR-3460: Add cloud-scripts directory and a zkcli.sh|bat tool for easy scripting and interaction with ZooKeeper. 2012-07-11 21:45:43 +00:00
contexts SOLR-3460: Add cloud-scripts directory and a zkcli.sh|bat tool for easy scripting and interaction with ZooKeeper. 2012-07-11 21:45:43 +00:00
etc fix log dir location 2012-07-12 11:58:24 +00:00
example-DIH SOLR-3313 Rename Query Type to Query Parser 2012-06-22 02:41:36 +00:00
exampledocs SOLR-2202: Money/Currency FieldType 2012-03-09 22:40:06 +00:00
lib LUCENE-3965: nuke bogus -ASL license.txt, this jar is not ASL. replace with the LICENSE-CDDL.txt from inside the jar 2012-04-18 03:36:33 +00:00
multicore LUCENE-4095: remove deprecations from trunk (just the easy ones for now) 2012-05-31 02:07:11 +00:00
solr SOLR-3660: Velocity: Link to admin page broken 2012-07-22 15:43:28 +00:00
README.txt SOLR-2616: Include a section about logging in the README 2012-07-12 11:16:42 +00:00
build.xml LUCENE-3892: revert the revert: configure fallbacks so that ivy downloads work from china 2012-04-27 01:01:04 +00:00
ivy.xml LUCENE-3930: nuke jars from source tree and use ivy 2012-03-30 18:04:43 +00:00
start.jar.sha1 LUCENE-3945: use sha1 checksums to verify jars pulled from ivy match expectations 2012-04-04 17:53:32 +00:00

README.txt

# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

Solr example configuration
--------------------------

To run the default example configuration, use 

  java -jar start.jar

in this example directory, and when Solr is started connect to 

  http://localhost:8983/solr/admin/

To add documents to the index, use the post.jar (or post.sh script) in
the exampledocs subdirectory (while Solr is running), for example:

     cd exampledocs
     java -jar post.jar *.xml
Or:  sh post.sh *.xml

See also README.txt in the solr subdirectory, and check
http://wiki.apache.org/solr/SolrResources for a list of tutorials and
introductory articles.

NOTE: This Solr example server references certain Solr jars outside of
this server directory for non-core modules with <lib> statements in
solrconfig.xml.  If you make a copy of this example server and wish
to use the ExtractingRequestHandler (SolrCell), DataImportHandler (DIH),
UIMA, the clustering component, or other modules in "contrib",
you will need to copy the required jars into solr/lib or update the paths to
the jars in your solrconfig.xml.

-SolrHome

By default, start.jar starts Solr in Jetty using the default solr home
directory of "./solr/" -- To run other example configurations, you can
speciy the solr.solr.home system property when starting jetty...

  java -Dsolr.solr.home=multicore -jar start.jar
  java -Dsolr.solr.home=example-DIH -jar start.jar

-Logging

By default, Solr will log to the console. This can be convenient when first
getting started, but eventually you will want to log to a file. To enable
logging, you can just pass a system property to Jetty on startup:

  java -Djava.util.logging.config.file=etc/logging.properties -jar start.jar
 
 This will use Java Util Logging to log to a file based on the config in
 etc/logging.properties. Logs will be written in the logs directory. It is
 also possible to setup log4j or other popular logging frameworks.