[FEATURE] Exists function in DeltaTableStep should not log error #70
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.
… run black
Description
The
exists
function of theDeltaTableStep
should notify the user about the non existence of the table with a different log level depending on the value of thecreate_if_not_exists
boolean flag (whereas now it is logging always with level error).If the flag is True than the log level is set to info. If the flag is False than the log level is set to error.
A possible alternative is to set the log level always to info or warning but this solution proposed already by the reporter looks more informative.
Related Issue
#34
Motivation and Context
Improving logging by making more informative and adeguate to the use case.
How Has This Been Tested?
By adding unit tests that verify the log message contains a certain string.
Screenshots (if appropriate):
Types of changes
Checklist: