Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python access to RasterSource doesn't expose JVM errors #267

Closed
vpipkt opened this issue Aug 8, 2019 · 1 comment · Fixed by #345

Comments

@vpipkt
Copy link
Member

commented Aug 8, 2019

See #263 and #266

Trying to take actions on these dataframes may result in a JVM stack trace with ERROR message that does not get to the JVM user. PYthon user just gets for example 0 count or empty list from a take

@vpipkt

This comment has been minimized.

Copy link
Member Author

commented Sep 2, 2019

Also see #319 and #174, those issues also expose this issue.

metasim added a commit to s22s/rasterframes that referenced this issue Sep 13, 2019
@metasim metasim closed this in #345 Sep 13, 2019
metasim added a commit to s22s/rasterframes that referenced this issue Sep 13, 2019
* develop: (254 commits)
  Incorporated PR feedback.
  Make python RasterSourceTest.test_list_of_list_of_str clearer, more stable
  Propagate errors encountered in RasterSourceToRasterRefs. Closes locationtech#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. Closes locationtech#343
  PR feedback edits.
  Fleshed out details on using Scala. Closes locationtech#324
  Fixes locationtech#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.
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.