Yicong-Huang opened a new issue, #6206:
URL: https://github.com/apache/texera/issues/6206

   ### What happened?
   
   Since #6185 (Arrow 19.0.0 upgrade), `computing-unit-managing-service` 
crashes at startup with `JsonMappingException: Scala module 2.18.8 requires 
Jackson Databind version >= 2.18.0 and < 2.19.0 - Found jackson-databind 
version 2.21.0`. That PR pinned the Jackson core family to 2.18.8 in 
`workflow-core`/`workflow-operator` to counter Arrow 19 evicting 
`jackson-databind` to 2.21.0, but the pin does not reach this service's own 
resolution: its dist bundles `jackson-databind-2.21.0.jar` next to 
`jackson-module-scala_2.13-2.18.8.jar` (the combination its own 
`LICENSE-binary` documents), while file-service and workflow-compiling-service 
correctly get 2.18.8 and boot fine. Expected: the service starts. Fix: apply 
the same Jackson pin/override to `ComputingUnitManagingService`.
   
   ### How to reproduce?
   
   On `main`, start the service (e.g. `bin/local-dev.sh up 
computing-unit-managing-service`); it exits immediately.
   
   ### Version/Branch
   
   1.3.0-incubating-SNAPSHOT (main)
   
   ### Commit Hash (Optional)
   
   4473a255d87e6f24b17ccbdaf812d8e587bfb1f2
   
   ### What browsers are you seeing the problem on?
   
   _No response_
   
   ### Relevant log output
   
   ```shell
   Exception in thread "main" 
com.fasterxml.jackson.databind.JsonMappingException: Scala module 2.18.8 
requires Jackson Databind version >= 2.18.0 and < 2.19.0 - Found 
jackson-databind version 2.21.0
        at 
com.fasterxml.jackson.module.scala.JacksonModule.setupModule(JacksonModule.scala:61)
        at 
org.apache.texera.service.ComputingUnitManagingService.initialize(ComputingUnitManagingService.scala:49)
        at 
org.apache.texera.service.ComputingUnitManagingService$.main(ComputingUnitManagingService.scala:92)
   ```


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