arorasimran0309 commented on PR #6635:
URL: https://github.com/apache/hive/pull/6635#issuecomment-5323658039

   > > About using jackson-bom, ...
   > 
   > You are right, I missed it. Thank you.
   > 
   > > ```
   > > As for com.fasterxml.jackson.core:jackson-annotations, version number 
2.21 is expected. It seems that is jackson versioning scheme and 
jackson-annotations uses minor version. As mentioned in jackson-bom:2.21.5:
   > > ```
   > 
   > and
   > 
   > > The jackson-dependencies: 2.12.7.1 from hadoop-common:3.4.2 in 
storage-api has scope ':provided' , which implies its not included in the final 
package (as seen above).
   > 
   > I'm not sure if I fully get it: Storage-API uses hadoop-common and it 
still uses an old version of jackson-databind:
   > 
   > ```
   > [INFO] |  +- 
com.fasterxml.jackson.core:jackson-databind:jar:2.12.7.1:provided
   > [INFO] |  |  +- 
com.fasterxml.jackson.core:jackson-annotations:jar:2.12.7:provided
   > ```
   > 
   > Provided means the artifact itself won't contain the given dependency but 
still, Hive will expects those versions - just receives it from a dependency. 
Is it anything against just excluding the old version here so that Hive won't 
requires the old version runtime?
   
   @InvisibleProgrammer You're right to question this. I have now added 
'jackson-bom:2.21.5' to **storage-api's** dependencyManagement (similar to 
standalone-metastore). This ensures storage-api compile with Jackson 2.21.5 
instead of 2.12.7.1 from hadoop-common. PFA the final dependency tree: 
   
[jackson_st-api.txt](https://github.com/user-attachments/files/31164996/jackson_st-api.txt)
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to