Google's server logs are stored as large collections of records (Protocol Buffers) that are partitioned over many disks within GFS. In order to perform calculations involving the logs, engineers can write MapReduce programs in C++ or Java. MapReduce programs need to be compiled and may be more verbose than necessary, so writing a program to analyze the logs can be time-consuming. To make it easier to write quick scripts, Rob Pike et al. developed the Sawzall language. A Sawzall script runs within the Map phase of a MapReduce and "emits" values to tables. Then the Reduce phase (which the script writer does not have to be concerned about) aggregates the tables from multiple runs into a single set of tables.
Currently, only the language runtime (which runs a Sawzall script once over a single input) has been open-sourced; the supporting program built on MapReduce has not been released.5
Some interesting features include:
Sawzall's design favors efficiency and engine simplicity over power:
This complete Sawzall program will read the input and produce three results: the number of records, the sum of the values, and the sum of the squares of the values.
Rob Pike, Sean Dorward, Robert Griesemer, Sean Quinlan. Interpreting the Data: Parallel Analysis with Sawzall http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/sv//archive/sawzall-sciprog.pdf ↩
Sawzall's open source project at Google Code. https://code.google.com/p/szl/ ↩
Discussion on which parts of Sawzall are open-source. https://groups.google.com/group/szl-users/browse_thread/thread/c0d90423d0fc27bd ↩
"Replacing Sawzall". 2015-12-04. Retrieved 2018-06-18. http://www.unofficialgoogledatascience.com/2015/12/replacing-sawzall-case-study-in-domain.html ↩