From c210a85813dc418ef0594508efaddd82494f6527 Mon Sep 17 00:00:00 2001 From: Kelly Innes Date: Fri, 28 Jul 2017 11:33:57 -0400 Subject: [PATCH] Fix two typos in ReadTheDocs docs - "it's decendents" -> "its descendants" - "SpaitalKey" -> "SpatialKey" --- docs/guide/spark.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guide/spark.rst b/docs/guide/spark.rst index c2e60691ea..bf969994b4 100644 --- a/docs/guide/spark.rst +++ b/docs/guide/spark.rst @@ -208,8 +208,8 @@ IO will happen right away in order to read the layer attributes from the ``AttributeStore``. However, the result of the call is an RDD, a description of the distributed collection at some point in the future. Consequently the distributed store (like HDFS or S3) will not touched -until some spark "action" is called on either ``rdd`` or one of it's -decedents. +until some spark "action" is called on either ``rdd`` or one of its +descendants. But what happens when IO gremlins strike and the type of the record stored does not match the type parameter? It depends. The layer reader @@ -471,7 +471,7 @@ us to verify that we're working with compatible layers. val rdd2: RDD[(SpatialKey, Tile)] with Metadata[TileLayerMetadata] = reader.read(getLayerId(2)) - val rdd3: TileLayerRDD[SpaitalKey] = + val rdd3: TileLayerRDD[SpatialKey] = reader.read(getLayerId(3)) Default Joins