-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility question #110
Comments
Effectively, from a technical point of view, it means no compatibility. SBDG directly depends on Spring Data for Apache Geode (SDG). The SBDG What does this mean exactly? Well, each generation / version of SBDG will invariably depend increasingly on newer versions of Spring Data, which in large part is actually guided by Spring Boot. Spring Boot is pulling in updated or newer versions of Spring Data (along with other Spring and 3rd party dependencies) with each generation (major version) as well as minor versions (major.minor). For example, Spring Boot By comparison, Spring Boot As the Version Compatibility Matrix outlines, even SBDG You have to go all the way back to SBDG
The reason is due to the relationship between Apache Geode and VMware Tanzu GemFire itself, and nothing to do with Spring in general, or all things Spring for Apache Geode bits in particular. VMware (Pivotal) stopped releasing standalone GemFire bits after Unfortunately, GemFire This is significant mainly since newer GemFire/Geode clients CANNOT communicate with older GemFire servers. This is a GemFire/Geode limitation, nothing to do with Spring. There is also the possibility that certain Apache Geode functions or behavior on which SDG would be based using a newer version of Apache Geode would not be available in the older GemFire versions. Therefore, it not 100% reliable to say that the Spring bits for Apache Geode at newer versions will be compatible and still work unhindered with older GemFire versions. We cannot make that claim and we certainly will not support the combination if something does not work, primarily because it is out of our control. Having said this... users have successfully downgraded newer versions of SBDG (e.g. This is especially true for users of VMware Tanzu GemFire for VMs (i.e. the old Pivotal Cloud Cache (PCC) on Pivotal CloudFoundry (PCF), now known as the VMware Tanzu Application Service for VMs). However, even VMware Tanzu GemFire for VMs is being rebased on Apache Geode, as you can see in the 1-14 docs (See "Software component version"). Anyway, while users have successfully done this, the mileage varies of course, and this is still not supported. Only product version combinations specifically listed in the Version Compatibility Matrix are specifically tested, approved and supported. Users who venture outside the compatible versions defined in the matrix do so at their own risk. Good question, but I hope this clarifies the matter. |
@jxblum Sincere thanks for the detailed response, it is very useful. We are going to take the matter up with our support team to decide on the best course of action. |
This question was just asked (again) on StackOverflow, here. BACKGROUND: To make this absolutely clear and to summarize.
PROBLEM: Technically, this is very much a GemFire/Geode problem and less to do with Spring, in general.
SOLUTION: As an experiment, I tried to downgrade the latest SBDG bits (as of this writing, that is
So that is:
See here. Even this upgrade was not trivial and risky! For example, it required a downgrade of Jackson JSON support in Spring Boot, where Boot So, there are risks either way you must weigh them accordingly. Regards |
Hi,
Are more recent versions of SBDG developed to work with Spring Boot 2.5.x and 2.6.x compatible with VMWare Tanzu GemFire versions 9.10.x? The compatibility information on the SBDG wiki states
NA
for this combination but I am not entirely sure if that means no compatibility or that it has not been tested.The text was updated successfully, but these errors were encountered: