[AI-FSSDK] [FSSDK-12750] Use attribute ID instead of key for CMAB prediction requests#456
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
The CMAB service's attribute filtering was using attribute keys as map keys in the filtered attributes passed to the prediction endpoint. The CMAB prediction API expects the attribute ID (not key) in the
"id"field of each attribute object. This fix ensures the filtered attributes map uses attribute IDs as keys so the downstream HTTP request sends the correct identifiers.Changes
filterAttributes()to store filtered attributes by attribute ID instead of attribute keyJira Ticket
FSSDK-12750