OpenSearch/docs/reference/index.asciidoc

[[elasticsearch-reference]]
= Elasticsearch Reference

include::../Versions.asciidoc[]


include::getting-started.asciidoc[]

include::setup.asciidoc[]

include::migration/index.asciidoc[]

include::api-conventions.asciidoc[]

include::docs.asciidoc[]

include::search.asciidoc[]

include::aggregations.asciidoc[]

include::indices.asciidoc[]

include::cat.asciidoc[]

include::cluster.asciidoc[]

include::query-dsl.asciidoc[]

include::mapping.asciidoc[]

include::analysis.asciidoc[]

include::modules.asciidoc[]

include::index-modules.asciidoc[]

include::ingest.asciidoc[]

include::how-to.asciidoc[]

include::testing.asciidoc[]

include::glossary.asciidoc[]

//////
 include::release-notes.asciidoc[]
//////

include::painless-api-reference.asciidoc[]

include::redirects.asciidoc[]
Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00			`[[elasticsearch-reference]]`
Docs: Rename reference docs to Elasticsearch Reference 2015-05-22 14:49:11 +02:00			`= Elasticsearch Reference`
Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00
Centralised doc versions in docs/Versions.asciidoc 2017-02-04 11:16:19 +01:00			`include::../Versions.asciidoc[]`
Generate reference links for painless API (#22775) Adds "Appending B. Painless API Reference", a reference of all classes and methods available from Painless. Removes links to java packages because they contain methods that we don't expose and don't contain methods that we do expose (the ones in Augmentation). Instead this generates a list of every class and every exposed method using the same type information available to the interpreter/compiler/whatever-we-call-it. From there you can jump to the relevant docs. Right now you build all the asciidoc files by running ``` gradle generatePainlessApi ``` These files are expected to be committed because we build the docs without running `gradle`. Also changes the output of `Debug.explain` so that it is easy to search for the class in the generated reference documentation. You can also run it in an IDE safely if you pass the path to the directory in which to generate the docs as the first parameter. It'll blow away the entire directory an recreate it from scratch so be careful. And then you can build the docs by running something like: ``` ../docs/build_docs.pl --out ../built_docs/ --doc docs/reference/index.asciidoc --open ``` That is, if you have checked out https://github.com/elastic/docs in `../docs`. Wait a minute or two and your browser will pop open in with all of Elasticsearch's reference documentation. If you go to `http://localhost:8000/painless-api-reference.html` you can see this list. Or you can get there by following the links to `Modules` and `Scripting` and `Painless` and then clicking the link in the paragraphs below titled `Appendix B. Painless API Reference`. I like having these in asciidoc because we can deep link to them from the rest of the guide with constructs like `<<painless-api-reference-Object-hashCode-0>>` and `<<painless-api-reference->>` and we get link checking. Then the only brittle link maintenance bit is the link generation for javadoc. Which sucks. But I think it is important that we link to the methods directly so they are easy to find. Relates to #22720 2017-01-26 10:39:19 -05:00

[DOCS] getting started tutorial 2014-04-18 13:51:59 -04:00			`include::getting-started.asciidoc[]`

Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00			`include::setup.asciidoc[]`

Core: Added the `index.query.parse.allow_unmapped_fields` setting to fail queries if they refer to unmapped fields. The percolator and filters in aliases by default enforce strict query parsing. Closes #7335 2014-07-18 22:50:07 +02:00			`include::migration/index.asciidoc[]`
[DOCS] Added breaking changes in 1.0 2014-01-15 17:50:24 +01:00
[DOCS] Reorganised common API conventions 2013-10-13 16:46:56 +02:00			`include::api-conventions.asciidoc[]`

Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00			`include::docs.asciidoc[]`

			`include::search.asciidoc[]`

[DOCS] Restructure Aggs documentation 2015-05-01 16:04:55 -04:00			`include::aggregations.asciidoc[]`

Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00			`include::indices.asciidoc[]`

First pass at cat docs. 2013-11-14 20:14:39 -05:00			`include::cat.asciidoc[]`

Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00			`include::cluster.asciidoc[]`

			`include::query-dsl.asciidoc[]`

			`include::mapping.asciidoc[]`

			`include::analysis.asciidoc[]`

			`include::modules.asciidoc[]`

			`include::index-modules.asciidoc[]`

Add ingest docs to the build 2016-02-11 14:16:56 -08:00			`include::ingest.asciidoc[]`

Add a how-to section to the docs. #18998 This moves the "Performance Considerations for Elasticsearch Indexing" blog post to the reference guide and adds similar recommendations for tuning disk usage and search speed. 2016-06-21 16:31:44 +02:00			`include::how-to.asciidoc[]`

[DOCS] Test framework documentation The java test framework using randomized testing is explained with a couple of examples. 2013-12-02 13:43:11 +01:00			`include::testing.asciidoc[]`

Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00			`include::glossary.asciidoc[]`

Use a comment block to comment out release notes 2016-09-08 18:30:37 +02:00			`//////`
			`include::release-notes.asciidoc[]`
			`//////`
Add release notes to docs index 2015-11-20 20:23:54 +01:00
Generate reference links for painless API (#22775) Adds "Appending B. Painless API Reference", a reference of all classes and methods available from Painless. Removes links to java packages because they contain methods that we don't expose and don't contain methods that we do expose (the ones in Augmentation). Instead this generates a list of every class and every exposed method using the same type information available to the interpreter/compiler/whatever-we-call-it. From there you can jump to the relevant docs. Right now you build all the asciidoc files by running ``` gradle generatePainlessApi ``` These files are expected to be committed because we build the docs without running `gradle`. Also changes the output of `Debug.explain` so that it is easy to search for the class in the generated reference documentation. You can also run it in an IDE safely if you pass the path to the directory in which to generate the docs as the first parameter. It'll blow away the entire directory an recreate it from scratch so be careful. And then you can build the docs by running something like: ``` ../docs/build_docs.pl --out ../built_docs/ --doc docs/reference/index.asciidoc --open ``` That is, if you have checked out https://github.com/elastic/docs in `../docs`. Wait a minute or two and your browser will pop open in with all of Elasticsearch's reference documentation. If you go to `http://localhost:8000/painless-api-reference.html` you can see this list. Or you can get there by following the links to `Modules` and `Scripting` and `Painless` and then clicking the link in the paragraphs below titled `Appendix B. Painless API Reference`. I like having these in asciidoc because we can deep link to them from the rest of the guide with constructs like `<<painless-api-reference-Object-hashCode-0>>` and `<<painless-api-reference->>` and we get link checking. Then the only brittle link maintenance bit is the link generation for javadoc. Which sucks. But I think it is important that we link to the methods directly so they are easy to find. Relates to #22720 2017-01-26 10:39:19 -05:00			`include::painless-api-reference.asciidoc[]`

Docs: Added stub entries for pages deleted from 1.x 2015-05-24 17:57:34 +02:00			`include::redirects.asciidoc[]`