LuciferYang commented on PR #48611:
URL: https://github.com/apache/spark/pull/48611#issuecomment-2601244783

   > After doing further research, I found out why there are these two warning 
logs in Spark 4.0 version, but not in Spark 3.x and earlier versions:
   > 
   > 1. When Spark 4.0 upgraded `jetty` 10 to 11, it also upgraded `jesery` 
2.41 to 3.0.12, related PR: [[SPARK-47118][BUILD][CORE][SQL][UI] Migrate from 
Jetty 10 to Jetty 11 #45154](https://github.com/apache/spark/pull/45154)
   > 2. Relevant changes in `jesery` 3.x 
version([eclipse-ee4j/jersey@c522d34](https://github.com/eclipse-ee4j/jersey/commit/c522d34d1c119ce84973978623b9d1fedd8da493)):
   > 
   > * MessagingBinders.java:
   >   `DATASOURCE("jakarta.activation.DataSource")` has been added to 
`EnabledProvidersBinder`.
   > * WadlFeature.java:
   >   Added some check logic and warning logs.
   > 
   > If the following two dependencies are in the class path, there will be no 
corresponding warning logs, but we excluded it in this PR: #25481 
`jakarta.activation:jakarta.activation-api` 
`jakarta.xml.bind:jakarta.xml.bind-api`
   
   We upgraded from 2.41 to 3.0.x. Actually, there was a similar registration 
in 2.41 as well, with just a slight difference in the namespace between `javax` 
and `jakarta`:
   
   
   
https://github.com/eclipse-ee4j/jersey/blob/3eac07f0b10ada9ba4828785ad2cc0ff5cf19f9f/core-common/src/main/java/org/glassfish/jersey/message/internal/MessagingBinders.java#L172
   
   
![image](https://github.com/user-attachments/assets/762786ce-efe0-4850-94e0-7e2470a1691d)
   
   
   Why didn't we need to make settings similar to the current pr before? I want 
to know if we revert the changes made by 
https://github.com/apache/spark/pull/25481, will the issue described in  
https://github.com/apache/spark/pull/25481 still exist? And could it also 
resolve the current problem?
   


-- 
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: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to