Repository navigation
Fix: Use configured TransformerDeID field names - #1224
Merged
Merged
Conversation
Route de-identification inputs through the model's configured feature and label keys.
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
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.
Issue
TransformerDeID.deidentify() always called the model with text= and labels=, even when the dataset configured different feature and label field names. Custom schemas therefore failed with a missing-key error
Fix
Build the de-identification call from self.feature_key and self.label_key so inference follows the field names established from the dataset schema
Notes
Regression test added