liferoad opened a new pull request, #36881:
URL: https://github.com/apache/beam/pull/36881

   This commit resolves all 31 compilation errors in the :runners:spark:4 
module, enabling successful compilation with Spark 4.0.0-preview2, Scala 2.13, 
and Java 17.
   
   Key changes:
   
   1. Scala 2.13 API Compatibility:
      - Replaced TraversableOnce with IterableOnce
      - Changed scala.Serializable to java.io.Serializable
      - Fixed union() method ambiguity by explicitly specifying type parameters
      - Modified ScalaInterop.seqOf() to return scala.collection.immutable.Seq
   
   2. ExpressionEncoder Constructor Migration:
      - Implemented reflection-based approach in EncoderFactory to handle Spark 
4.x API changes
      - Attempts to use ExpressionEncoder.apply with FlatEncoder wrappers
      - Added @SuppressWarnings("nullness") for Checker Framework compatibility
   
   3. updateStateByKey Signature Adaptation:
      - Created Function2 adapter in SparkGroupAlsoByWindowViaWindowSet
      - Wrapped iterator-based UpdateStateByKeyFunction to match Spark 4.x 
signature
      - Changed from Seq to scala.collection.immutable.Seq
   
   4. Nullness Annotations:
      - Added @SuppressWarnings("nullness") in EvaluationContext for Checker 
Framework
   
   Fixes #36841
   
   **Please** add a meaningful description for your change here
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable. This will automatically add a link to the 
pull request in the issue. If you would like the issue to automatically close 
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI or the [workflows 
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) 
to see a list of phrases to trigger workflows.
   


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