preserve conflicting objects when parent object is being deleted

[harshavardhana]

Community Contribution License

All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.

Description

preserve conflicting objects when the parent object is being deleted

Motivation and Context

a/prefix
a/prefix/1.txt

where a/prefix is an object that does not have /
in the end, we do not have to aggressively recursively
delete all the sub-folders as well. Instead, convert
the call into self-contained to delete 'xl.meta'
and then subsequently attempt to Remove the parent.

How to test this PR?

Well create conflicting objects such as these

mc cp /etc/hosts myminio/testbucket/prefix (first object)
mc cp /etc/hosts myminio/testbucket/prefix/hosts (conflicting object, with parent as object)

mc rm myminio/testbucket/prefix --force

Would end up deleting prefix/hosts as well in the current release,
changing this behavior to only delete myminio/testbucket/prefix
not the conflicting object.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Optimization (provides speedup with no functional changes)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Fixes a regression (If yes, please add commit-id or PR # here)
• Unit tests added/updated
• Internal documentation updated
• Create a documentation update request here

[shtripat]

LGTM. Verified

[vadmeste]

what about when an object has some data-dirs ? removing parent is not aggressive

[harshavardhana]

what about when an object has some data-dirs ? removing parent is not aggressive

if you can generate same data-dir uuid's please show me how :-)

[vadmeste]

LGTM