You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: 01_Search_in_depth.asciidoc
+17-17Lines changed: 17 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
-
= placeholder1
2
-
1
+
ifndef::es_build[= placeholder1]
2
+
3
3
[[search-in-depth]]
4
4
= Search in Depth
5
5
@@ -27,18 +27,18 @@ Search is not just about full-text search: a large portion of your data will
27
27
be structured values like dates and numbers. We will start by explaining how
28
28
to combine structured search((("structured search", "combining with full text search")))((("full text search", "combining with structured search"))) with full-text search in the most efficient way.
Copy file name to clipboardExpand all lines: Preface.asciidoc
+78-12Lines changed: 78 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -117,40 +117,95 @@ are more standalone and can be referred to as needed.
117
117
118
118
This book is divided into seven parts:
119
119
120
-
* Chapters pass:[<a href="#intro">1</a>] through pass:[<a href="#inside-a-shard">11</a>] provide an introduction to Elasticsearch. They
120
+
ifndef::es_build[]
121
+
122
+
* Chapters pass:[<a href="#intro">1</a>] through pass:[<a href="#inside-a-shard">11</a>]
123
+
provide an introduction to Elasticsearch. They
121
124
explain how to get your data in and out of Elasticsearch, how Elasticsearch
122
125
interprets the data in your documents, how basic search works, and how to
123
126
manage indices. By the end of this section, you will already be able to
124
-
integrate your application with Elasticsearch. Chapters pass:[<a href="#distributed-cluster">2</a>], pass:[<a href="#distributed-docs">4</a>], pass:[<a href="#distributed-search">9</a>], and pass:[<a href="#inside-a-shard">11</a>] are
125
-
supplemental chapters that provide more insight into the distributed
127
+
integrate your application with Elasticsearch. Chapters pass:[<a href="#distributed-cluster">2</a>], pass:[<a href="#distributed-docs">4</a>], pass:[<a href="#distributed-search">9</a>], and pass:[<a href="#inside-a-shard">11</a>]
128
+
are supplemental chapters that provide more insight into the distributed
126
129
processes at work, but are not required reading.
127
130
128
-
* Chapters pass:[<a href="#structured-search">12</a>] through pass:[<a href="#controlling-relevance">17</a>] offer a deep dive into search--how to index and
131
+
* Chapters pass:[<a href="#structured-search">12</a>] through pass:[<a href="#controlling-relevance">17</a>]
132
+
offer a deep dive into search--how to index and
129
133
query your data to allow you to take advantage of more-advanced concepts
130
134
such as word proximity, and partial matching. You will understand how
131
135
relevance works and how to control it to ensure that the best results are
132
136
on the first page.
133
137
134
-
* Chapters pass:[<a href="#language-intro">18</a>] through pass:[<a href="#fuzzy-matching">23</a>] tackle the thorny subject of dealing with human
138
+
* Chapters pass:[<a href="#language-intro">18</a>] through pass:[<a href="#fuzzy-matching">23</a>]
139
+
tackle the thorny subject of dealing with human
135
140
language through effective use of analyzers and queries. We start with
136
141
an easy approach to language analysis before diving into the complexities
137
142
of language, alphabets, and sorting. We cover stemming, stopwords, synonyms,
138
143
and fuzzy matching.
139
144
140
-
* Chapters pass:[<a href="#_high_level_concepts">24</a>] through pass:[<a href="#_controlling_memory_use_and_latency">34</a>] discuss aggregations and analytics--ways to
141
-
summarize and group your data to show overall trends.
145
+
* Chapters pass:[<a href="#aggs-high-level">24</a>] through pass:[<a href="#controlling-memory">34</a>]
146
+
discuss aggregations and analytics--ways to summarize and group your data to show overall trends.
142
147
143
-
* Chapters pass:[<a href="#_closing_thoughts">35</a>] through pass:[<a href="#geo-aggs">38</a>] present the two approaches to geolocation
148
+
* Chapters pass:[<a href="#geopoints">35</a>] through pass:[<a href="#geo-shapes">38</a>] CHECK CHAPTERS HERE
149
+
present the two approaches to geolocation
144
150
supported by Elasticsearch: lat/lon geo-points, and complex geo-shapes.
145
151
146
-
* Chapters pass:[<a href="#geo-shapes">39</a>] through pass:[<a href="#parent-child">42</a>] talk about how to model your data to work
152
+
* Chapters pass:[<a href="#relations">39</a>] through pass:[<a href="#scale">42</a>] CHECK CHAPTERS HERE
153
+
talk about how to model your data to work
147
154
most efficiently with Elasticsearch. Representing relationships
148
155
between entities is not as easy in a search engine as it is in
149
156
a relational database, which has been designed for that purpose.
150
157
These chapters also explain how to suit your index design to
151
158
match the flow of data through your system.
152
159
153
-
* Finally, Chapters pass:[<a href="#scale">43</a>] through pass:[<a href="#cluster-admin">44</a>] discuss moving to production: the important configurations, what to monitor, and how to diagnose and prevent problems.
160
+
* Finally, Chapters pass:[<a href="#cluster-admin">43</a>] through pass:[<a href="#post_deploy">44</a>] CHECK CHAPTERS HERE
161
+
discuss moving to production: the important configurations, what to monitor, and how to diagnose and prevent problems.
162
+
163
+
endif::es_build[]
164
+
165
+
ifdef::es_build[]
166
+
167
+
* Chapters <<intro>> through <<inside-a-shard>> provide an introduction to Elasticsearch. They
168
+
explain how to get your data in and out of Elasticsearch, how Elasticsearch
169
+
interprets the data in your documents, how basic search works, and how to
170
+
manage indices. By the end of this section, you will already be able to
171
+
integrate your application with Elasticsearch. Chapters
172
+
<<distributed-cluster>>, <<distributed-docs>>, <<distributed-search>>, and <<inside-a-shard>>
173
+
are supplemental chapters that provide more insight into the distributed
174
+
processes at work, but are not required reading.
175
+
176
+
* Chapters <<structured-search>> through <<controlling-relevance>>
177
+
offer a deep dive into search--how to index and
178
+
query your data to allow you to take advantage of more-advanced concepts
179
+
such as word proximity, and partial matching. You will understand how
180
+
relevance works and how to control it to ensure that the best results are
181
+
on the first page.
182
+
183
+
* Chapters <<language-intro>> through <<fuzzy-matching>>
184
+
tackle the thorny subject of dealing with human
185
+
language through effective use of analyzers and queries. We start with
186
+
an easy approach to language analysis before diving into the complexities
187
+
of language, alphabets, and sorting. We cover stemming, stopwords, synonyms,
188
+
and fuzzy matching.
189
+
190
+
* Chapters <<aggs-high-level>> through <<controlling-memory>>
191
+
discuss aggregations and analytics--ways to summarize and group your data to show overall trends.
192
+
193
+
* Chapters <<geopoints>> through <<geo-shapes>>
194
+
present the two approaches to geolocation
195
+
supported by Elasticsearch: lat/lon geo-points, and complex geo-shapes.
196
+
197
+
* Chapters <<relations>> through <<scale>>
198
+
talk about how to model your data to work
199
+
most efficiently with Elasticsearch. Representing relationships
200
+
between entities is not as easy in a search engine as it is in
201
+
a relational database, which has been designed for that purpose.
202
+
These chapters also explain how to suit your index design to
203
+
match the flow of data through your system.
204
+
205
+
* Finally, Chapters <<cluster-admin>> through <<post_deploy>>
206
+
discuss moving to production: the important configurations, what to monitor, and how to diagnose and prevent problems.
207
+
208
+
endif::es_build[]
154
209
155
210
There are three topics that we do not cover in this book, because they are evolving rapidly and anything we
156
211
write will soon be out-of-date:
@@ -197,10 +252,19 @@ Do not edit this section.
197
252
198
253
This book is here to help you get your job done. In general, if example code is offered with this book, you may use it in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.
199
254
200
-
We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: “_Elasticsearch: The Definitive Guide_ by Clinton Gormley and Zachary Tony (O’Reilly). Copyright 2014 Elasticsearch BV, 978-0-596-xxxx-x.”
255
+
We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: ``_Elasticsearch: The Definitive Guide_ by Clinton Gormley and Zachary Tony (O’Reilly). Copyright 2014 Elasticsearch BV, 978-0-596-xxxx-x.''
256
+
257
+
ifndef::es_build[]
258
+
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at pass:[<a class="email" href="mailto:[email protected]"><em>[email protected]</em></a>].
262
+
ifdef::es_build[]
263
+
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at
0 commit comments