ivancich

How can we address the limits omap's limits place on the number of versions of an object?

Assumption: everything below is referring to versioned buckets.

== The Issue ==
* a current limit is that all metadata for versions of one object must be on a single bucket index shard
* bucket index objects for versioned buckets use two omap entries per version
* omap has a "soft" limit of 100K entries
* Once reached, warnings are logged
* So that would max out at around 50K versions for an object *if* one bucket index shard were devoted to one object, which is unlikely with our current hashed bucket index scheme