Progress commit for review
move conf initialization to TestEnvironment
Refactored TestEnvironment to use hadoop Paths
Added 'Add' local operation and test
removed erroneously added eclipse plugin
remove unnecessary 'extends MustMatcher' from tests
Created a separate trait called SparkEnvironment for SparkContext creation
- This trait can be mixed in by only those tests that need a Spark context
Another attempt at SparkContext creation in tests.
SparkEnvironment then looks like this
- a myIt that users call instead of it. myIt ends up calling it
- a setup/tearDown that actually creates and frees the mutable context variable
The second point is why I don't like this too much as users need to call this
in every suite that uses SparkContext
minor change: organize imports
Another attempt at SparkContext creation in tests.
This one uses fixture.FunSpec.withFixture to pass in the SparkContext
to the tests.
Pros
- Remove SparkEnvironment
Cons
- Had to add a separate TestEnvironmentFixture that is the same as
TestEnvironment except for withFixture.
Refactored TestEnvironment to reduce code duplication
Cleanup TestEnvironment
minor change: add comments to TestEnvironment
replace call to SparkUtils.createSparkContext in TestEnvironment
add test->test dependency on root in spark
add more tests to TileIdPartitionerSpec
Added a more functional RasterReader
- Supports range and points lookups
- this is called RasterReader, the older one moved to SimpleRasterReader
- Added a test
minor change: formatting
Add range() method to TileIdPartitioner
Add to Add the ability to add two rasters :)