Made minor edits to match the proposed Estimator transformSchema mehtod to the existing Model transformSchema method. #61
Conversation
This file contains 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
…od to the existing Model transformSchema method.
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.
Small edits on top of #60.
In particular:
Includes checks and schema modifications similar to what was already done in the Model class. Both the Estimator and the Model will:
This ensures that the Estimator’s schema transformation is consistent with the eventual Model’s schema, making it clear to downstream pipeline stages what the final output schema will be.
The PR code adds explicit checks that the predictionCol and scoreCol do not already exist. This is a good safeguard to prevent accidental overwrites of existing columns.