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:
vs a simple:
|Field||Original Value||New Value|
|Attachment||0001-BIGTOP-844.-Apache-Hadoop-rpm-upgrade-sequence-is-br.patch [ 12568534 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|