suryaprasanna opened a new pull request, #17941:
URL: https://github.com/apache/hudi/pull/17941

   ### Describe the issue this Pull Request addresses
   
   IntelliJ IDE fails to run unit tests because it expects Parquet version 
1.10.1 to be present, but when building with the default Maven profile 
(spark3.5), the actual version used is 1.13.1. This version mismatch causes 
IDE-based test execution to fail.
   
   ### Summary and Changelog
   
   Updated the default Parquet version from 1.10.1 to 1.13.1 to align with the 
version used by the default spark3.5 Maven profile.
   
   **Changes:**
   - Changed `parquet.version` from 1.10.1 to 1.13.1 in root pom.xml
   - Changed `hive.parquet.version` from 1.10.1 to 1.13.1 in root pom.xml
   
   This ensures IDE environments (like IntelliJ) use the same Parquet version 
as the default Maven build, eliminating version mismatch issues during test 
execution.
   
   ### Impact
   
   This change improves the developer experience by fixing IDE-based unit test 
execution. Users who need to override the Parquet version can still do so using 
Maven profiles.
   
   ### Risk Level
   
   **Low** - This aligns the default version with what is already being used by 
the default spark3.5 profile, so no functional changes are expected. The 
version 1.13.1 is already well-tested through existing CI/CD pipelines using 
the spark3.5 profile.
   
   ### Documentation Update
   
   None - This is an internal build configuration change that doesn't affect 
user-facing functionality or APIs.
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable


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