pttydou opened a new pull request, #3278:
URL: https://github.com/apache/sedona/pull/3278

   ## 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 
#3277.
   
   ## What changes were proposed in this PR?
   
   `StacUtils.addFiltersToUrl` now detects an existing decoded `datetime` query 
parameter name and preserves the endpoint value instead of appending a pushed 
temporal parameter. Other query bytes and fragments stay unchanged, and a 
spatial `bbox` can still be added.
   
   Regression coverage includes valid, empty, malformed, repeated, and 
percent-encoded endpoint parameters.
   
   ## How was this patch tested?
   
   - `mvn -B -ntp -Drat.skip=true -Dlog4j.version=2.19.0 -pl spark/common 
test-compile`
   - `mvn -B -ntp -Dlog4j.version=2.19.0 
-DwildcardSuites=org.apache.spark.sql.sedona_sql.io.stac.StacBatchUrlTest,org.apache.spark.sql.sedona_sql.io.stac.StacUtilsTest
 -pl spark/common scalatest:test` (40/40, Scala 2.12)
   - `mvn -B -ntp -Drat.skip=true -Dlog4j.version=2.19.0 -Dscala=2.13 
-Dspark=3.4 -pl spark/common clean test-compile`
   - `mvn -B -ntp -Dlog4j.version=2.19.0 -Dscala=2.13 -Dspark=3.4 
-DwildcardSuites=org.apache.spark.sql.sedona_sql.io.stac.StacBatchUrlTest,org.apache.spark.sql.sedona_sql.io.stac.StacUtilsTest
 -pl spark/common scalatest:test` (40/40)
   - `mvn -B -ntp -pl spark/common spotless:apply`
   
   ## Did this PR include necessary documentation updates?
   
   - No, this PR does not affect any public API so no need to change the 
documentation.
   


-- 
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