fix: use TemporaryDirectory instead of NamedTemporaryFile for MLTable… #3618
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CynicDog
requested review from
kingernupur,
jayesh-tanna,
achauhan-scc and
imatiach-msft
as code owners
|
@microsoft-github-policy-service agree |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR improves the way temporary MLTable data is handled and uploaded in the model monitoring preprocessing script.
Key change:
tempfile.NamedTemporaryFilewithtempfile.TemporaryDirectorywhen saving the MLTable object before uploading to Azure Machine Learning.Before:
The MLTable was saved using
NamedTemporaryFile, resulting in a single-file output path.After:
Switched to
TemporaryDirectory, which better reflects MLTable's directory-based format and avoids issues during upload.