Errata

Fundamentals of Data Engineering

Errata for Fundamentals of Data Engineering

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page Acknowlegments
technical reviewers paragraph

Tod Hanseman should be spelled Tod Hansmann

Joe Reis
 
Jul 22, 2022  Jul 28, 2023
Page section "lambda Architecture" page 104
figure 3-14

The figure 3-14 illustrating the lambda architecture doesn't illustrate what is described in the paragraph above it.
the author says : "In a Lambda architecture (Figure 3-14), you have systems operating independently of each other—batch, streaming, and serving."
In the figure we have 2 streaming systems (the batch system is not shown) and a serving system.

Note from the Author or Editor:
The bottom box that says "stream processing" that attaches to "batch processing" should say "batch processing".

Anonymous  Nov 15, 2022  Jul 28, 2023
Page Acknowledgments - page xix
Upper section

Lior Gavish is mentioned twice

Note from the Author or Editor:
Please remove the second reference to Lior Gavish in acknowlegements

Igal drayerman  Feb 10, 2023  Jul 28, 2023
Printed
Page page 241, or in the Frequency sub section
middle image

Figure 7-4 shows ingestion frequencies of data in batch, micro batch, and real time. The sub headings of frequent and semi-frequent are in the wrong order.

It should be

batch = semi-frequent
micro-batch = frequent

Joe Reis
 
Jul 31, 2023 
Page Page Number: 273
Section - Data Definition Language, 2nd Paragraph

On Page Number 273, within the Data Definition Language section, there it is mentioned in para2 that classifies "UPDATE" as a DDL expression. However, it should be noted that "UPDATE" is typically considered as a DML expression.

Note from the Author or Editor:
Thanks for spotting this error.

Divyansh Jain  Nov 16, 2023 
Page p.307
l. -3.

The line
"That's it! Now let’s look at ways to view data contextually using satellites.'
does not seem to fit in this place

The line should be just below the table 8-18, and above the 'Satelites' paragraph.

Note from the Author or Editor:
This might read better if we move the "That's it! Now let’s look at ways to view data contextually using satellites.' sentence to the end of the Link section, after the sentence that says "Note that we're...". This is the sentence right before the satellite portion begins.

HIDEMOTO NAKADA  Jan 14, 2024 
Page 168
2nd paragraph

"...which we discuss at greater length in 'Messages and Streams' on page 167.)" should probably read, "...which we discuss at greater length in 'Message Queues and Event-Streaming Platforms' on page 259.)". In its current form, this is a self-referential breadcrumb, and the preceding paragraphs in the section do not "discuss at greater length," whereas the aforementioned section starting on page 259 does go into more detail. This is a particularly confusing typo due to the section name. Indeed, I did not understand the parenthetical until 100 pages later!

Note from the Author or Editor:
O'Reilly - can we fix this? Thanks.

Adam Shamlian  Nov 16, 2022  Jul 28, 2023
Page 174
Bottom of page

The JSON object printed at the bottom of this page is not formatted properly for some of the nested data. It makes reading and interpreting what this data represents quite difficult.

The two lines after the lines starting with "name" ("first" and "last") should have two additional leading spaces. Same for four lines after "favorite_bands".

Joe Reis, co-author, sent me to this link after we discussed this on LinkedIn. I would be more than happy to volunteer to help out with helping fix formatting.

Note from the Author or Editor:
O'Reilly - can we better format this? Thanks.

Brian Armstrong  Dec 12, 2022  Jul 28, 2023
Page 184
3rd page paragraph; 1st paragraph in subsection "Topics."

The last sentence of the paragraph reads, "A topic can have zero, one, or multiple producers and customers on most event-streaming platforms."

It should probably read, "A topic can have zero, one, or multiple producers and consumers on most event-streaming platforms."

So, "consumers", not "customers ".

Note from the Author or Editor:
Confirmed. Please correct.

L. D. Nicolas May  Aug 27, 2023 
Page 219
First paragraph

In the first paragraph there is a reference to a figure that reads (see Figure 6-3).

It should reference Figure 6-2.

Note from the Author or Editor:
Confirmed

Mike Porter  Sep 03, 2023 
Printed
Page 287
Not sure, got feedback from someone

Page 287 "if new events arrive for the use" should be user

Joe Reis
 
Feb 11, 2023  Jul 28, 2023