|Pivotal GemFire||All versions|
As described here, Pivotal does not offer support for Geode, the Open Source version of GemFire. This article goes more into the differences between Geode and GemFire.
Jars and Libraries
Q: Which libraries or Jars are completely shared between Geode and GemFire? Which are not?
A: The source between Geode and GemFire is shared, but will not always be in sync. The binaries will be different because they will typically be released at different points in time. GemFire releases will have a much higher level of testing. If you have questions about which product is running you can check:
- `gfsh version --full`
- The Jar names will match the GemFire $VERSION
- The Jar manifests will state that the product is GemFire, not Geode
Q: Does the Pivotal Commercial Repository for GemFire contain sources for Geode libraries?
A: Geode and GemFire sources are not always aligned. Firstly, GemFire may not yet contain all of the code that exists in Geode. Secondly, GemFire is a complete recompile of all code, Geode or not. Thus, it does not depend on Geode maven artifacts.
Releases and Fixes
Q: Let's say there are some minor fixes already checked into Geode but not in GemFire (speaking of common libraries here). Can it happen? How often will Pivotal be overwriting the full GemFire source code with Geode source code?
A: Pivotal does not directly control the release schedule for Geode, so there is no guarantee when a fix will show up in a Geode release. Pivotal will be issuing GemFire maintenance releases on a regular cadence.
Matching source code
Q: Is there any guarantee that what you see in the Geode source code is the same as what Pivotal distributes with GemFire (for common libraries)?
A: There is no guarantee that the Geode sources exactly match the GemFire sources. In fact, that’s one reason to purchase GemFire—so you can have a supported, stable version of Geode.