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.
On 1/23/19 1:26 PM, gtotsline wrote:
Hi Mike -
Thanks for responding so quickly, it's greatly appreciated. The
ConditionalWriter does not appear to address our use case where we actually
want to suppress Accumulo versioning of a record based on the value in the
record that was read vs. input data our system receives. Is there a way to
dynamically suppress Accumulo record versioning?
--
Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html
