Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BugFix] Minimise mumber of calls to folder create in case of Blob to File Copy #2591

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

pranavmalik-msft
Copy link
Collaborator

Description:
This pull request addresses a regression stemming from the existing logic for Blob to File Copy. Previously, the default case returned a nullFolderTracker, lacking the mechanism to track already created folders. Considering this a corner case, the proposed solution introduces the AllFolderCopy approach. With this enhancement, the foldertracker logic now effectively monitors previously created folders, thereby reducing redundant folder creation during Blob to File operations.

Changes:

  • Introduced the AllFolderCopy approach to address the regression in Blob to File Copy, effectively resolving the identified issue.

Copy link
Member

@siminsavani-msft siminsavani-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any way to test this?

@@ -674,6 +674,12 @@ func NewFolderPropertyOption(fromTo common.FromTo, recursive, stripTopDir bool,
}
}

// In case of a Blob to File Copy, we will go for all folder copy
if fromTo == common.EFromTo.BlobFile() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we decided to use the mitigation (customer sets include directory flag) and get to this issue in a later release after we have a solid plan?

@seanmcc-msft @vibhansa-msft thoughts?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can consider this fix for the next release (not for 10.23). Once we have more clarity on the flow, may be we can improvise the fix.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to consider the part where putting such check may take away the capabilities to skip empty folders while copying.

Copy link
Member

@adreed-msft adreed-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is neither a proper fix to the issue (If the source has no directory stubs, the issue resurfaces), nor is it what was discussed (temp mitigation by manual flag setting, spike for next release)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants