| commit | 4ef985d2d3a985ddcf33050bdf11ee43f1365ab7 | [log] [tgz] |
|---|---|---|
| author | David Smiley <dsmiley@apache.org> | Wed May 31 01:00:04 2023 -0400 |
| committer | David Smiley <dsmiley@apache.org> | Wed May 31 01:00:04 2023 -0400 |
| tree | d3ced9ea9291b9063594791056e936ca95d456a0 | |
| parent | b2361c04d45378355f986777cd6f81574aeab2bd [diff] |
CHANGES.txt add Jason Baik
Solr is the popular, blazing fast open source search platform for all your enterprise, e-commerce, and analytics needs, built on Apache Lucene.
For a complete description of the Solr project, team composition, source code repositories, and other details, please see the Solr web site at https://solr.apache.org/
Downloads for Apache Solr distributions are available at https://solr.apache.org/downloads.html.
The Reference Guide contains an entire Deployment Guide to walk you through installing Solr.
You can run Solr in Docker via the official image. Learn more about Solr in Docker
Solr has official support for running on Kubernetes, in the official Docker image. Please refer to the Solr Operator home for details, tutorials and instructions.
Solr includes a few examples to help you get started. To run a specific example, enter:
bin/solr start -e <EXAMPLE> where <EXAMPLE> is one of:
cloud: SolrCloud example
techproducts: Comprehensive example illustrating many of Solr's core capabilities
schemaless: Schema-less example (schema is inferred from data during indexing)
films: Example of starting with _default configset and adding explicit fields dynamically
For instance, if you want to run the techproducts example, enter:
bin/solr start -e techproducts
For a more in-depth introduction, please check out the tutorials in the Solr Reference Guide.
#solr on libera.chatPlease review CONTRIBUTING.md for information on contributing to the project.
To get involved in the developer community:
#solr-dev in the the-asf organization. Sign up at https://the-asf.slack.com/messages/CE70MDPMF#solr-dev on libera.chatLearn more about developing Solr by reading through the developer docs in ./dev-docs source tree.