james-willis opened a new pull request, #3321:
URL: https://github.com/apache/sedona/pull/3321

   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor 
Development Guide](https://sedona.apache.org/latest/community/develop/)
   
   ## Is this PR related to a ticket?
   
   - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes #3320
   
   ## What changes were proposed in this PR?
   
   `RS_Resample` and `RS_ReprojectMatch` silently fell back to NearestNeighbor 
for any algorithm name other than `nearestneighbor`/`bilinear`/`bicubic` — a 
typo like `'biliner'` or another engine's vocabulary like `'CubicSpline'` 
quietly returned wrong-interpolation results. 
`RasterEditors.createInterpolationAlgorithm` now throws 
`IllegalArgumentException` naming the accepted values. A null or empty 
algorithm keeps its documented default of NearestNeighbor, and the accepted 
spellings are unchanged.
   
   Surfaced by the SedonaDB↔Sedona Spark parity suite (apache/sedona-db 
`integration/spark-parity`), where SedonaDB rejects unknown names and the 
silent fallback shows up as a cataloged divergence.
   
   ## How was this patch tested?
   
   Two new unit tests (`testResampleUnknownAlgorithm`, 
`testReprojectMatchUnknownAlgorithm`) assert the error through both public 
entry points; the full `RasterEditorsTest` class passes locally (29 tests, JDK 
17), and `mvn spotless:apply` is clean.
   
   ## Did this PR include necessary documentation updates?
   
   - No, this PR does not affect any public API so no need to change the 
documentation. (The docs do not describe the silent fallback; the accepted 
algorithm names are unchanged.)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to