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
This is the first piece of the "Collections API", which is the ability to work with collections of (key, value) pairs in a similar way to using RDDs, without the overhead of Spark.
This task is to read a collection of tiles from the backends. We can already read in single values (e.g. Tiles), and RDDs of tiles. With the completion of this task, we will read some collection of values (e.g. Vector[(SpatialKey, Tile)]) out of the backend. This should be able to use the Query API to query the backend in order to produce the collection.
A potential interface for this type of reader is follows, which is distinctly similar to FilteringLayerReader
This is the first piece of the "Collections API", which is the ability to work with collections of (key, value) pairs in a similar way to using RDDs, without the overhead of Spark.
This task is to read a collection of tiles from the backends. We can already read in single values (e.g. Tiles), and RDDs of tiles. With the completion of this task, we will read some collection of values (e.g.
Vector[(SpatialKey, Tile)]
) out of the backend. This should be able to use the Query API to query the backend in order to produce the collection.A potential interface for this type of reader is follows, which is distinctly similar to
FilteringLayerReader
This might require us to have a similar type as
ContextRDD
for the collection type, e.g.ContextCollection
The text was updated successfully, but these errors were encountered: