JiaLiangC opened a new pull request, #1225:
URL: https://github.com/apache/bigtop/pull/1225

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'BIGTOP-3638: Your PR title ...'.
   -->
   
   ### Description of PR
   Spark 3.3 itself does support parallel compilation. However, Spark 3.3 uses 
Maven Shade Plugin version 3.2.4, which triggers an infinite loop bug during 
parallel compilation. You can find more details about this issue at 
[MSHADE-413](https://issues.apache.org/jira/browse/MSHADE-413).
   
   A PR has been submitted for Spark 3.3 to upgrade the Maven Shade Plugin to 
version 3.5.0. This upgrade has already been applied in Spark 3.5, 
[SPARK-44257](https://issues.apache.org/jira/browse/SPARK-44257).
   
   Therefore, this PR includes the upgrade of the mvn-shade-plugin as part of 
[SPARK-44257](https://issues.apache.org/jira/browse/SPARK-44257). It's worth 
noting that [SPARK-44257](https://issues.apache.org/jira/browse/SPARK-44257) 
contains some code that doesn't exist in Spark 3.3 and has been ignored.
   
   depend on [BIGTOP-4044](https://issues.apache.org/jira/browse/BIGTOP-4044)
   
   ### How was this patch tested?
   <img width="902" alt="image" 
src="https://github.com/apache/bigtop/assets/18082602/0ef08aba-a83b-47ba-9c6c-86b9fadb4dc7";>
   
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'BIGTOP-3638. Your PR title ...')?
   - [ ] Make sure that newly added files do not have any licensing issues. 
When in doubt refer to https://www.apache.org/licenses/


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