DocumentMutation.delete()

Operations Performed

Deletes the field without first checking whether the field exists. All fields below the deleted field are also deleted, even if the application does not have write permission on the subfields. The only exception is if a column family is defined on a subfield. In this case, the column family persists and remains accessible.

If the field does not exist, this method silently returns without doing anything.

Example of Deleting a Scalar Field

Original document

{ 
  "_id" : "000001",
  "a" : {
         "b" : 1,
         "c" : 3 
         }
} 

Example code for the deletion

  public DocumentMutation buildDocumentMutation() {
    return MapRDB.newDocumentMutation()
      .delete("a.c");
  }

  public void deleteField(String tablePath, DocumentMutation mutation, String _id) {
    try(Table table = MapRDB.getTable(tablePath)) {
      table.update(_id, mutation);
    }
  }

Parameter	Description
_id	The value of the document's _id field.
tablePath	The path of the table in the MapR file system. See Table Paths.

Revised document

{ 
  "_id" : "000001",
  "a" : {
         "b" : 1
         }
}

Permissions Required

• The writeAce permission on the volumes where the JSON tables that contain the documents are located. For information about how to set permissions on volumes, see Setting/Modifying Whole Volume ACEs.
• writeperm on the field to delete. See How to Obtain readperm or writeperm on a Field.

Link to Javadoc

DocumentMutation