[
https://issues.apache.org/jira/browse/SEDONA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714613#comment-17714613
]
Adam Binford commented on SEDONA-276:
-------------------------------------
[~umartin] I had everything use the same logging implementation for tests to
simplify writing log4j configs to control the outputs of the test. Otherwise
you end up with older Spark tests using log4j1 and newer ones using log4j2, so
you need to maintain both config files to control test output. If there's
anything that is still using log4j1 APIs that should definitely be switched to
only use slf4j, I added the log4j-1.2-api as an interim solution until all of
that gets resolved/updated.
> Add support for Spark 3.4
> -------------------------
>
> Key: SEDONA-276
> URL: https://issues.apache.org/jira/browse/SEDONA-276
> Project: Apache Sedona
> Issue Type: Improvement
> Reporter: Martin Andersson
> Priority: Major
>
> Spark 3.4.0 was announced on April 14.
> [https://lists.apache.org/thread/o1o9n1t036rmfp45q1jrjs0zzzx0j156]
> Findings from a quick test build using -Dspark.version=3.4.0:
> # Incompatible logging api versions causes test failures.
> # GeoParquet and Geotiff datasources fails to compile due to api changes in
> Spark.
> Setting log4j and slf4j to the same versions as Spark 3.4.0 uses solves 1. I
> don't know how that will affect other Spark versions.
> To solve 2 we might need to use reflection to handle the api changes in Spark.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
