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
I'm guessing something changed between Spark 2.2 and 2.3 that we didn't catch because the unit tests around Parquet IO in EncodingSpec only counted rows, and didn't perform any action that realized the tiles.
* develop: (254 commits)
Incorporated PR feedback.
Make python RasterSourceTest.test_list_of_list_of_str clearer, more stable
Propagate errors encountered in RasterSourceToRasterRefs. Closeslocationtech#267.
Updated release notes.
Switched Explode tiles to use UnsafeRow for slight improvement on memory pressure. Reworked TileExplodeBench
Changed CatalystSerialize implementations to store scheams as fields rather than methods.
Benchmark and fix for CellType reification issue. Closeslocationtech#343
PR feedback edits.
Fleshed out details on using Scala. Closeslocationtech#324Fixeslocationtech#338.
Tweaked parquet I/O tests to trigger UDT issue.
Normalize RasterSourceDataSource param names between python and SQL
PR feedback
Run python tile exploder test for projected raster
Fix for locationtech#333 and additional tests in that vein.
Add failing unit test for issue 333, error in rf_agg_local_mean
Updated ExplodeTiles to work with proj_raster type.
Ignoring RGB composite tests until next round of improvements.
IT test build fix.
Incremental work on refactoring aggregate raster creation.
...
I'm guessing something changed between Spark 2.2 and 2.3 that we didn't catch because the unit tests around Parquet IO in
EncodingSpec
only counted rows, and didn't perform any action that realized the tiles.The text was updated successfully, but these errors were encountered: