accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1346) deleterows should take a -r option
Date Fri, 10 May 2013 14:55:17 GMT


Keith Turner commented on ACCUMULO-1346:

Just noticed there is also a bug in the shell docs.  It states the begin row is inclusive
in one place and exclusive in another place.

usage: deleterows [-?] [-b <begin-row>] [-e <end-row>] [-f] [-t <table>]
description: deletes a range of rows in a table.  Note that rows matching the start row ARE
NOT deleted, but rows matching the end row ARE deleted.
  -?,--help                      display this help
  -b,--begin-row <begin-row>     begin row (inclusive)
  -e,--end-row <end-row>         end row (inclusive)
  -f,--force                     delete data even if start or end are not specified
  -t,--table <table>             table to delete a row range from

There is another way this task could accomplished.  Create an iterator that when it sees row
X, it seeks over it.  1.5 adds the ability to have per compaction iterators.  So just the
tablet with the offending row could be compacted with this special iterator.  This could possibly
serve as an implementation for deleterows -r.

In 1.4 the special iterator would have to be configured for the entire table, and then a compaction
could be forced on the tablet containing the row.  This should be safe in 1.4 as long as the
iterator is well behaved.  

> deleterows should take a -r option
> ----------------------------------
>                 Key: ACCUMULO-1346
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: shell
>    Affects Versions: 1.4.2
>            Reporter: Mike Drob
>            Assignee: Drew Farris
>            Priority: Minor
>              Labels: hackathon, hackation-5-2013
> deleterows only allows an exclusive begin row and an inclusive end row. This is difficult
to use for deleting a single (large) row. It would be nice if a user could specify -r, similar
to scan.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message