What about creating a separate table to keep the history, with versioning and write to this table when appropriate?
On Wed, Jan 23, 2019 at 2:26 PM gtotsline <[email protected]> wrote: > Mike Miller-2 wrote > >> Is there a way to dynamically suppress Accumulo record versioning? > > > > Not that I know of but perhaps others have come up with ways to do this. > > > > What if you set the maxVersions on your table to 1 (config -t mytable -s > > table.iterator.majc.vers.opt.maxVersions=1) and use conditional mutation > > to > > determine whether to update or not? Then you wouldn't have to worry about > > versions, just updating the data based on input. > > The problem is, we want versions of a record to be created for some change > cases for the record while in others change cases for the same record we do > not (some changes are very high volume so we want to avoid filling up the > DB > while still using it to maintain a version history select set of > updates). > > > > -- > Sent from: http://apache-accumulo.1065345.n5.nabble.com/Developers-f3.html >
