Make KeyToValueMapping API consistent #2426
Merged
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
Codecov Report
@@ Coverage Diff @@
## master #2426 +/- ##
=========================================
Coverage ? 71.25%
=========================================
Files ? 785
Lines ? 140895
Branches ? 16105
=========================================
Hits ? 100388
Misses ? 36041
Partials ? 4466
|
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #2376
Makes KeyToValueMapping API consistent with the rest by using the
string outputColumnName, string inputColumnName = nullsignature in theMapKeyToValuemethod inConversionsExtensionsCatalogand the associatedKeyToValueMappingEstimatorandKeyToValueMappingTransformerconstructors.