Major Description
Here's the deal – during the RPM upgrade sequence there's a point in time when files that have different names in new and old package exist side-by-side. What it means for our style of hadoop packaging is that we'll have both /usr/lib/hadoop/foo-<old version>.jar and /usr/lib/hadoop/foo-<new version>.jar getting onto the classpath when we issue a condrestart for any service.
This is pretty bad.
At this point my knee jerk reaction is to re-evaluate why do we need versioned jars to begit with. Do you guys think there's any value in something like:
- /usr/lib/hadoop/hadoop-common-2.0.0.jar
vs a simple:
- /usr/lib/hadoop/hadoop-common.jar