In addition to the involved entities described in {@link SourceCodeChange} a delete has a
parentEntity that describes from which entity changedEntity isdeleted. Speaking of an AST, parentEntity describes the node in which changedEntity was a child before the delete. parentEntity is taken from the left AST, i.e., old version.DELETE method implementation.
@author Pier Fumagalli
To delete an entire row, instantiate a Delete object with the row to delete. To further define the scope of what to delete, perform additional methods as outlined below.
To delete specific families, execute {@link #deleteFamily(byte[]) deleteFamily}for each family to delete.
To delete multiple versions of specific columns, execute {@link #deleteColumns(byte[],byte[]) deleteColumns}for each column to delete.
To delete specific versions of specific columns, execute {@link #deleteColumn(byte[],byte[],long) deleteColumn}for each column version to delete.
Specifying timestamps, deleteFamily and deleteColumns will delete all versions with a timestamp less than or equal to that passed. If no timestamp is specified, an entry is added with a timestamp of 'now' where 'now' is the servers's System.currentTimeMillis(). Specifying a timestamp to the deleteColumn method will delete versions only with a timestamp equal to that specified. If no timestamp is passed to deleteColumn, internally, it figures the most recent cell's timestamp and adds a delete at that timestamp; i.e. it deletes the most recently added cell.
The timestamp passed to the constructor is used ONLY for delete of rows. For anything less -- a deleteColumn, deleteColumns or deleteFamily -- then you need to use the method overrides that take a timestamp. The constructor timestamp is not referenced.
Delete...
Deletes files or directories.
@author Hans DockterDelete class.
@author dgreen @version $Id: $ | |