// The above means that any added/deleted fields are incompatible.
//
//msgp:tuple VolInfo
type VolInfo struct {
	// Name of the volume.
	Name string

	// Date and time when the volume was created.
	Created time.Time

	// total VolInfo counts
	count int

	// Date and time when the volume was deleted, if Deleted
	Deleted time.Time
}

    }

    /**
     * Deletes all documents associated with the specified session ID from the given index.
     *
     * @param searchEngineClient the search engine client to use for deletion
     * @param index the index name to delete documents from
     * @param sessionId the session ID to delete documents for
     * @return the number of documents that were deleted
     */

        // Test that deleting already deleted file doesn't throw
        Path tempFile = Files.createTempFile("already_deleted", ".tmp");
        Files.delete(tempFile);
        assertFalse(Files.exists(tempFile));

        // Should return false without throwing
        boolean deleted = Files.deleteIfExists(tempFile);
        assertFalse(deleted);
    }

    @Test

        // Log the result
        if (sizeBeforeDeletion > 0) {
            logger.info("Successfully deleted {} crawling info log(s) using bulk delete", sizeBeforeDeletion);
        } else {
            logger.info("No crawling info logs to delete (may have been deleted by previous test)");
        }
    }

					if len(l.lockMap) != locks {
						t.Fatalf("objects deleted, want %d != got %d", locks, len(l.lockMap))
					}
					if len(l.lockUID) != locks*readers {
						t.Fatalf("objects deleted, want %d != got %d", locks*readers, len(l.lockUID))
					}

					// Expire 50%
					expired := time.Now().Add(-time.Hour * 2)

        // For each of 4 indices: delete old + delete backup = 8 deletes
        assertEquals(8, testClient.deletedIndices.size());
        // Verify original index names appear in deleted list (old index deletion at step 3)
        boolean foundOriginalDelete = false;
        for (final String deleted : testClient.deletedIndices) {
            if (!deleted.contains(".backup.") && !deleted.contains(".rebuild.")) {

success.delete_doc_from_index = Started a process to delete documents from an index.
success.crawling_info_delete_all = Deleted session data.
success.start_crawl_process = Started a crawl process.
success.upload_design_file = Updated {0}.
success.update_design_jsp_file = Updated {0}.
success.create_crawling_config_at_wizard = Created a crawling config {0}.
success.failure_url_delete_all = Deleted failure URLs.
success.delete_file = Deleted {0} file.

success.delete_doc_from_index = Started a process to delete documents from an index.
success.crawling_info_delete_all = Deleted session data.
success.start_crawl_process = Started a crawl process.
success.upload_design_file = Updated {0}.
success.update_design_jsp_file = Updated {0}.
success.create_crawling_config_at_wizard = Created a crawling config {0}.
success.failure_url_delete_all = Deleted failure URLs.
success.delete_file = Deleted {0} file.

		case objectlock.RetGovernance:
			// In governance mode, users can't overwrite or delete an object
			// version or alter its lock settings unless they have special
			// permissions. With governance mode, you protect objects against
			// being deleted by most users, but you can still grant some users
			// permission to alter the retention settings or delete the object
			// if necessary. You can also use governance mode to test retention-period

case of versioned deletes a.k.a permanent delete of a version by doing a `mc rm --version-id` on a object, replication implementation marks a object version permanently deleted as `PENDING` purge and deletes the version from source after syncing to the target and ensuring target version is deleted. The delete marker being deleted or object version being deleted will still be visible on listing with `mc ls --versions` until the sync is completed. Objects marked as deleted will not be accessible via `GET`...