deleteRows should be fine with a combiner, but it's probably not going to be efficient for small ranges. ACCUMULO-3235 should make it more efficient, but it'll still probably add a split point and (very) briefly take tablets offline.
On Mon, Nov 30, 2015 at 12:46 PM z11373 <z11...@outlook.com> wrote: > Revisit this thread... > I just want to know if deleteRows is not appropriate for a table with > summing combiners? > The problem with scan and for each putDelete is it's consuming more memory, > though from my test it is way faster than calling deleteRows for this > particular case. > > Thanks, > Z > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/delete-rows-test-result-tp15569p15634.html > Sent from the Developers mailing list archive at Nabble.com. >
