Josh Elser-2 wrote > Why are you trying to do this in the first place? When you write a new > version of a cell, you are essentially replacing the old value. Leaving > the old value in the table and lazily removing it (via compaction) is a > core optimization to the write-path for Accumulo (from BigTable itself). > > I'm having a hard time understanding why you're trying to do what you're > asking.
Hi Josh - The reason we are trying to do this is that we have two competing requirements: 1. Maintain an unbounded versioned history of a certain subset or types of updates (for audit and forensics purposes) for a row 2. Do not add to that row's versioned history for a certain other subset or types of updates. So in the same table we want to take advantage of Accumulo's versioning for some change cases for a record, while for others we would like to avoid new versions being created because of the very high volume of changes anticipated. Thanks. -- Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
