- Elasticsearch Server: Second Edition
- Rafa? Ku? Marek Rogoziński
- 223字
- 2021-04-02 10:07:35
Conventions
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows:
"The postings format is a per-field property, just like type
or name
."
A block of code is set as follows:
{ "status" : 200, "name" : "es_server", "version" : { "number" : "1.0.0", "build_hash" : "a46900e9c72c0a623d71b54016357d5f94c8ea32", "build_timestamp" : "2014-02-12T16:18:34Z", "build_snapshot" : false, "lucene_version" : "4.6" }, "tagline" : "You Know, for Search" }
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
{ "mappings" : { "post" : { "properties" : { "id" : { "type" : "long", "store" : "yes", "precision_step" : "0" }, "name" : { "type" : "string", "store" : "yes", "index" : "analyzed", "similarity" : "BM25" }, "contents" : { "type" : "string", "store" : "no", "index" : "analyzed", "similarity" : "BM25" } } } } }
Any command-line input or output is written as follows:
curl -XGET http://localhost:9200/blog/article/1