Go to file
Chris Hegarty 8d96bbe3bf Fix sql JdbcDocCsvSpecIT test {docs.testFilterToday} failing (#109274)
This commit fixes an SQL test that hardcodes expected results based on today's date. The docs.testFilterToday test needs to be updated since June 2 2024, because Anneke's hire-date of 1989-06-02 (35 years ago as of time of writing) affects the expected output.
2024-06-03 09:44:03 +01:00
.buildkite Bump versions after 8.13.4 release 2024-05-10 21:38:45 +00:00
.ci Bump versions after 8.13.4 release 2024-05-10 21:38:45 +00:00
.github Update and pin gradle wrapper validation action (#106635) 2024-03-21 19:17:25 -04:00
.idea Don't apply IntelliJ illegal module dependency inspection to test code (#101977) 2023-11-09 12:46:18 -05:00
benchmarks Add an optimised int8 vector distance function for aarch64. (#106133) 2024-04-12 08:44:21 +01:00
build-conventions Harden usage of XML document builder in build-conventions (#106874) 2024-03-31 19:41:52 -04:00
build-tools Move muted tests file and allow for additional files to be configured (#107916) (#107924) 2024-04-29 13:11:27 -04:00
build-tools-internal Update bundled JDK to Java 22 (again) (#108654) (#108686) 2024-05-15 13:12:04 -04:00
client Upgrade Mockito dependency (#108637) (#108644) 2024-05-14 17:55:50 -04:00
dev-tools Add an optimised int8 vector distance function for aarch64. (#106133) 2024-04-12 08:44:21 +01:00
distribution Fix G1 JDK bug workaround (#108641) (#108653) 2024-05-14 20:35:57 -04:00
docs Wrap "Pattern too complex" exception into an IllegalArgumentException (#109173) (#109255) 2024-05-31 19:47:00 +02:00
docs-mdx/painless [DOCS] Adds an MDX file for testing purposes. (#106165) 2024-03-11 15:57:00 +01:00
gradle Update bundled JDK to Java 22 (again) (#108654) (#108686) 2024-05-15 13:12:04 -04:00
libs [8.14] Fix multithreading copies in lib vec (#108802) (#108810) 2024-05-19 12:15:14 -04:00
licenses
modules Wrap "Pattern too complex" exception into an IllegalArgumentException (#109173) (#109255) 2024-05-31 19:47:00 +02:00
plugins Migrate YAML REST tests to synthetic cluster feature check (#107068) 2024-04-11 18:22:38 +02:00
qa Increase startup timeout in packaging tests (#108487) (#108489) 2024-05-09 20:13:02 -04:00
rest-api-spec [8.14] Extend the Health API basic YAML tests (#108811) (#109111) 2024-05-29 03:17:35 -04:00
server Wrap "Pattern too complex" exception into an IllegalArgumentException (#109173) (#109255) 2024-05-31 19:47:00 +02:00
test ESQL: Stop sending version in tests (#108961) (#108984) 2024-05-24 09:09:33 +02:00
x-pack Fix sql JdbcDocCsvSpecIT test {docs.testFilterToday} failing (#109274) 2024-06-03 09:44:03 +01:00
.backportrc.json Bump to version 8.14.0 2024-02-14 18:05:43 +00:00
.dir-locals.el
.editorconfig SQL: Fix FORMAT function to better comply with Microsoft SQL Server specification (#86225) 2022-05-18 12:03:00 +02:00
.git-blame-ignore-revs Update .git-blame-ignore-revs 2023-04-04 10:05:42 +01:00
.gitattributes
.gitignore Fix ESQL tests in IntelliJ (#107313) 2024-04-11 13:44:56 -04:00
BUILDING.md Spelling and grammar fixes in repository docs (#102345) 2023-11-18 15:05:02 +00:00
CHANGELOG.md In the field capabilities API, re-add support for `fields` in the request body (#88972) 2022-08-04 13:44:50 -04:00
CONTRIBUTING.md Add cluster def link to CONTRIBUTING.md (#102979) 2023-12-05 14:29:21 +01:00
LICENSE.txt
NOTICE.txt
README.asciidoc Update README.asciidoc (#103597) 2024-03-04 11:31:00 +01:00
REST_API_COMPATIBILITY.md [DOCS] Update tech preview copy (#101606) 2023-10-31 10:31:07 -04:00
TESTING.asciidoc Adding option to debug the cli launcher (#102464) 2023-11-28 10:26:09 +01:00
TRACING.md Update/Cleanup references to old tracing.apm.* legacy settings in favor of the telemetry.* settings (#104917) 2024-01-31 09:20:05 +01:00
Vagrantfile
branches.json Remove 8.12 from branches.json 2024-03-26 13:03:24 -04:00
build.gradle [ci] Move multi-node tests from check part2 to part5 (#107553) (#108026) 2024-04-29 13:35:56 -04:00
catalog-info.yaml [buildkite] Re-enable platform-support periodic pipelines (#99552) 2023-09-13 16:21:28 -04:00
gradle.properties Suppress gradle welcome messages (#102898) 2023-12-03 02:08:12 +01:00
gradlew Update gradle wrapper to 8.4 (#99856) 2023-10-11 17:02:27 +02:00
gradlew.bat Update Gradle wrapper to 8.6 (#103796) 2024-02-13 11:13:29 -08:00
muted-tests.yml Mute org.elasticsearch.analysis.common.CommonAnalysisClientYamlTestSuiteIT org.elasticsearch.analysis.common.CommonAnalysisClientYamlTestSuiteIT #109266 2024-05-31 16:52:38 -04:00
settings.gradle Port krb5kdc to test container and rework hdfs handling (#106228) 2024-03-26 08:39:39 +01:00

README.asciidoc

= Elasticsearch

Elasticsearch is a distributed search and analytics engine optimized for speed and relevance on production-scale workloads. Elasticsearch is the foundation of Elastic's open Stack platform. Search in near real-time over massive datasets, perform vector searches, integrate with generative AI applications, and much more.

Use cases enabled by Elasticsearch include:

* https://www.elastic.co/search-labs/blog/articles/retrieval-augmented-generation-rag[Retrieval Augmented Generation (RAG)] 
* https://www.elastic.co/search-labs/blog/categories/vector-search[Vector search]
* Full-text search
* Logs
* Metrics
* Application performance monitoring (APM)
* Security logs

\... and more!

To learn more about Elasticsearch's features and capabilities, see our
https://www.elastic.co/products/elasticsearch[product page].

To access information on https://www.elastic.co/search-labs/blog/categories/ml-research[machine learning innovations] and the latest https://www.elastic.co/search-labs/blog/categories/lucene[Lucene contributions from Elastic], more information can be found in https://www.elastic.co/search-labs[Search Labs]. 

[[get-started]]
== Get started

The simplest way to set up Elasticsearch is to create a managed deployment with
https://www.elastic.co/cloud/as-a-service[Elasticsearch Service on Elastic
Cloud].

If you prefer to install and manage Elasticsearch yourself, you can download
the latest version from 
https://www.elastic.co/downloads/elasticsearch[elastic.co/downloads/elasticsearch].

=== Run Elasticsearch locally

//// 
IMPORTANT: This content is replicated in the Elasticsearch guide. 
If you make changes, you must also update setup/set-up-local-dev-deployment.asciidoc.
////

To try out Elasticsearch on your own machine, we recommend using Docker
and running both Elasticsearch and Kibana.
Docker images are available from the https://www.docker.elastic.co[Elastic Docker registry].

NOTE: Starting in Elasticsearch 8.0, security is enabled by default. 
The first time you start Elasticsearch, TLS encryption is configured automatically, 
a password is generated for the `elastic` user, 
and a Kibana enrollment token is created so you can connect Kibana to your secured cluster.

For other installation options, see the
https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html[Elasticsearch installation documentation].

**Start Elasticsearch**

. Install and start https://www.docker.com/products/docker-desktop[Docker
Desktop]. Go to **Preferences > Resources > Advanced** and set Memory to at least 4GB.

. Start an Elasticsearch container:
+
----
docker network create elastic
docker pull docker.elastic.co/elasticsearch/elasticsearch:{version} <1>
docker run --name elasticsearch --net elastic -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" -t docker.elastic.co/elasticsearch/elasticsearch:{version}
----
<1> Replace {version} with the version of Elasticsearch you want to run.
+
When you start Elasticsearch for the first time, the generated `elastic` user password and
Kibana enrollment token are output to the terminal.
+
NOTE: You might need to scroll back a bit in the terminal to view the password 
and enrollment token.

. Copy the generated password and enrollment token and save them in a secure 
location. These values are shown only when you start Elasticsearch for the first time.
You'll use these to enroll Kibana with your Elasticsearch cluster and log in.

**Start Kibana**

Kibana enables you to easily send requests to Elasticsearch and analyze, visualize, and manage data interactively.

. In a new terminal session, start Kibana and connect it to your Elasticsearch container:
+
----
docker pull docker.elastic.co/kibana/kibana:{version} <1>
docker run --name kibana --net elastic -p 5601:5601 docker.elastic.co/kibana/kibana:{version}
----
<1> Replace {version} with the version of Kibana you want to run.
+
When you start Kibana, a unique URL is output to your terminal.

. To access Kibana, open the generated URL in your browser.

  .. Paste the enrollment token that you copied when starting
  Elasticsearch and click the button to connect your Kibana instance with Elasticsearch.

  .. Log in to Kibana as the `elastic` user with the password that was generated
  when you started Elasticsearch.

**Send requests to Elasticsearch**

You send data and other requests to Elasticsearch through REST APIs. 
You can interact with Elasticsearch using any client that sends HTTP requests, 
such as the https://www.elastic.co/guide/en/elasticsearch/client/index.html[Elasticsearch
language clients] and https://curl.se[curl]. 
Kibana's developer console provides an easy way to experiment and test requests. 
To access the console, go to **Management > Dev Tools**.

**Add data**

You index data into Elasticsearch by sending JSON objects (documents) through the REST APIs.  
Whether you have structured or unstructured text, numerical data, or geospatial data, 
Elasticsearch efficiently stores and indexes it in a way that supports fast searches. 

For timestamped data such as logs and metrics, you typically add documents to a
data stream made up of multiple auto-generated backing indices.

To add a single document to an index, submit an HTTP post request that targets the index. 

----
POST /customer/_doc/1
{
  "firstname": "Jennifer",
  "lastname": "Walters"
}
----

This request automatically creates the `customer` index if it doesn't exist, 
adds a new document that has an ID of 1, and 
stores and indexes the `firstname` and `lastname` fields.

The new document is available immediately from any node in the cluster. 
You can retrieve it with a GET request that specifies its document ID:

----
GET /customer/_doc/1
----

To add multiple documents in one request, use the `_bulk` API.
Bulk data must be newline-delimited JSON (NDJSON). 
Each line must end in a newline character (`\n`), including the last line.

----
PUT customer/_bulk
{ "create": { } }
{ "firstname": "Monica","lastname":"Rambeau"}
{ "create": { } }
{ "firstname": "Carol","lastname":"Danvers"}
{ "create": { } }
{ "firstname": "Wanda","lastname":"Maximoff"}
{ "create": { } }
{ "firstname": "Jennifer","lastname":"Takeda"}
----

**Search**

Indexed documents are available for search in near real-time. 
The following search matches all customers with a first name of _Jennifer_ 
in the `customer` index.

----
GET customer/_search
{
  "query" : {
    "match" : { "firstname": "Jennifer" }  
  }
}
----

**Explore**

You can use Discover in Kibana to interactively search and filter your data.
From there, you can start creating visualizations and building and sharing dashboards.

To get started, create a _data view_ that connects to one or more Elasticsearch indices,
data streams, or index aliases.

. Go to **Management > Stack Management > Kibana > Data Views**.
. Select **Create data view**.
. Enter a name for the data view and a pattern that matches one or more indices, 
such as _customer_. 
. Select **Save data view to Kibana**.  

To start exploring, go to **Analytics > Discover**.

[[upgrade]]
== Upgrade

To upgrade from an earlier version of Elasticsearch, see the
https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html[Elasticsearch upgrade
documentation].

[[build-source]]
== Build from source

Elasticsearch uses https://gradle.org[Gradle] for its build system.

To build a distribution for your local OS and print its output location upon
completion, run:
----
./gradlew localDistro
----

To build a distribution for another platform, run the related command:
----
./gradlew :distribution:archives:linux-tar:assemble
./gradlew :distribution:archives:darwin-tar:assemble
./gradlew :distribution:archives:windows-zip:assemble
----

To build distributions for all supported platforms, run:
----
./gradlew assemble
----

Distributions are output to `distribution/archives`.

To run the test suite, see xref:TESTING.asciidoc[TESTING].

[[docs]]
== Documentation

For the complete Elasticsearch documentation visit
https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html[elastic.co].

For information about our documentation processes, see the
xref:docs/README.asciidoc[docs README].

[[examples]]
== Examples and guides

The https://github.com/elastic/elasticsearch-labs[`elasticsearch-labs`] repo contains executable Python notebooks, sample apps, and resources to test out Elasticsearch for vector search, hybrid search and generative AI use cases.


[[contribute]]
== Contribute

For contribution guidelines, see xref:CONTRIBUTING.md[CONTRIBUTING]. 

[[questions]]
== Questions? Problems? Suggestions?

* To report a bug or request a feature, create a
https://github.com/elastic/elasticsearch/issues/new/choose[GitHub Issue]. Please
ensure someone else hasn't created an issue for the same topic.

* Need help using Elasticsearch? Reach out on the
https://discuss.elastic.co[Elastic Forum] or https://ela.st/slack[Slack]. A
fellow community member or Elastic engineer will be happy to help you out.