ostinru commented on issue #1805:
URL: https://github.com/apache/cloudberry/issues/1805#issuecomment-4624357501

   > 1- For using PXF2.1, do we need to opt minor upgrade CB server from 2.0 to 
2.1 ? As we see, pxf2.1 has compatibility issues with CB2.0 server. Is that 
correct understanding !!
   
   cloudberry-pxf 2.1 was first release. We built it with cloudberry 2.1 in 
mind. And, it seems that cloudberry extensions captures cloudberry version 
during build, and then asserts at runtime. I have created an issue to keep 
backward compatibility in next (2.2) versions.
   https://github.com/apache/cloudberry-pxf/issues/115
   
   Upgrade CB2.0 -> 2.1 should solve compatibility issues. However please test 
upgrade on dev cluster before production. I heard that there are minor 
`pg_catalog`(?) changes between 2.0 and 2.1, so be careful.
   
   Alternatively - you can build cloudberry-pxf 2.1 with cloudberry 2.0 from 
sources. It should be compatible. I am not sure that we will rebuild pxf-2.1 
for cloudberry-2.0. Apache release process is tricky.
   
   > 2- We are on KVM and not VMWare, does that still put the Spring-Boot 
vulnerable ?
   
   Spring Boot is a collection of java libraries created by SpringSource. 
SpringSource was acquired by VMWare. Then moved to Pivotal. And acquired by 
VMWare again. So, VMWare (as company) continues Spring Boot development.
   So, there is nothing about virtualization, it was about VMWare as company. 
And yes, it will be vulnerable if you expose PXF port to the public.
   
   > 3- Updating Spring-Boot to 3.5.x or 4.0.x, that mean, it would be there 
with CB3.0 with pxf-3.0 release ?
   
   Yes. This is our plan.


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