Class DeleteBucketRequest

    • Constructor Detail

      • DeleteBucketRequest

        public DeleteBucketRequest​(java.lang.String bucketName,
                                   boolean recursivelyDeleteAllData)
      • DeleteBucketRequest

        public DeleteBucketRequest​(java.lang.String bucketName)
    • Method Detail

      • getHeaders

        public java.util.Map<java.lang.String,​java.util.List<java.lang.Object>> getHeaders()
        Description copied from class: ObjectRequest
        Override to return request-specific headers based on properties of the request. Always call super() first and modify the result.
        Overrides:
        getHeaders in class ObjectRequest
      • isRecursivelyDeleteAllData

        public boolean isRecursivelyDeleteAllData()
        It is the trigger to use the new bucket deletion feature. The current delete operation is a synchronous operation, when recursivelyDeleteAllData is default set to false.. When recursivelyDeleteAllData comes to true, the request becomes asynchronous and will return immediately. The bucket will be marked as "delete in progress". The bucket will be read-only through S3 and will not allow reads/writes through NFS (for FS bucket). Background tasks will be initiated across all of the associated zones and tables to remove objects/versions associated with the buckets. Once all tasks have completed the bucket will be deleted from the system. It must be noted that the issue of object lock and governance must not be overlooked for such an operation. It must be noted that the operation will delete all objects and data in the bucket and it cannot be undone. It is only supported on ECS version 3.8 or above.
      • withRecursivelyDeleteAllData

        public DeleteBucketRequest withRecursivelyDeleteAllData​(boolean recursivelyDeleteAllData)