The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| PDF |
Page 1
1 |
Something is wrong with the PDF version. It doesn't open on Apple Preview, the default PDF reader on Mac OS X.
I've used Apple Preview for years to open PDF files from all kinds and sizes and never had any issues.
When I open the PDF version from this book, it gets terribly slow to the point where the computer almost freezes.
It's not just my machine. I've tested it on a brand new MacBook running the latest OS X, and the same issue persists.
The only way I can open it is by using Adobe Acrobat. But I don't want to use it since it's too clumsy.
Pleas, would it be possible to fix the PDF version?
Thank you.
|
Felipe Dornelas |
Dec 05, 2015 |
| PDF |
Page 20
Last sentence before section Analytics |
Unfinished sentence
"You can read more about the highlighting of search snippets in the"
|
Darren Davie |
Oct 18, 2014 |
| PDF |
Page 38
4th and 5th paragraph |
I mentioned just one page here, but several pages in the pdf seem to have formatting errors for monospaced text.
e.g.
The ID is a string that, when combined with the _index and _type, uniquely identifies a document in Elasticsearch.
|
Sandip Bhattacharya |
Mar 11, 2015 |
| PDF |
Page 43
Last sentence in section Updating a Whole Document |
I don't understand the following sentence
"The only difference is that the update API achieves this through a single client request, instead of requiring separate get and index requests."
When I did the update all I did was do a post. PUT /website/blog/123
How is that separate get and index requests?
Need more wording to clarify.
|
Darren Davie |
Oct 18, 2014 |
| PDF |
Page 51
tip box |
Unfinished sentence
"You can read more about scripting in the"
|
Darren Davie |
Oct 18, 2014 |
| PDF |
Page 86
2/3 of way down |
GET /_analyze?analyzer=standard
Text to analyze
"Text to analyze" should be wrapped in curly brackets / braces for the query to work properly.
|
Anonymous |
Mar 21, 2015 |
| Printed |
Page 89
tip on 2nd paragraph |
The paragraf did not end properly it reads:
The type values like <ALPHANUM> vary per analyzer and can be ignor-
ed. The only place that they are used in Elasticshearch is in the
I think it should end with "analyze step" but I don't know
|
Jose Luis Perez Diez |
Nov 27, 2014 |
| Printed |
Page 137
2nd paragraph under Token Filters |
There are sentence fragments and words missing in the paragraph.
|
Timothy Yoder |
Mar 24, 2016 |
| PDF |
Page 410
3rd bullet point at top of page |
On page 410 of the pdf version of the book, the 3rd bullet point from the top of the page states
"Deletion of a character:: b_l_ack → back"
I think that "::" should be ":"
|
Robert Lucente |
May 19, 2015 |
| Printed |
Page 575
Heading |
On page 575 you talk about "parent and child relationships"
If you google for this, most result are about recursive data structures.
The type of the parent is the same as of the child. It is like in the real world: The parent was a child, and the parent of the parent .... same types: human beings.
But in the example parent and child can have different types.
Maybe "master detail" would fit better here:
http://en.wikipedia.org/wiki/Master%E2%80%93detail_interface
==========================
Second issue
I am missing a chapter about ELK: LogStash, ElasticSearch an Kibana.
Beside these two minor issues, the book was a pleasure to read! Thank you.
|
Thomas Güttler |
Mar 02, 2015 |