DOC-6661 feature store use case#3388
Merged
Merged
Conversation
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
Contributor
dwdougherty
approved these changes
Jun 1, 2026
Collaborator
dwdougherty
left a comment
There was a problem hiding this comment.
Just one material comment; otherwise, LGTM.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 75b4fc1. Configure here.
EliShteinman
added a commit
to EliShteinman/docs
that referenced
this pull request
Jun 2, 2026
DOC-6661 Feature store use case example
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.

Not finished yet - this is just to get the Bugbot feedback as early as possible.
Note
Medium Risk
Large documentation and demo surface with concurrency-sensitive worker/reset patterns and Redis 7.4 HEXPIRE semantics; incorrect examples could mislead operators, but no production runtime or auth changes.
Overview
Adds a new Redis feature store use-case hub and client walkthroughs with runnable fraud-scoring demos: per-entity hashes at
fs:user:{id}, batchHSET+ keyEXPIRE, streaming updates withHEXPIRE/HTTL(Redis 7.4+),HMGETinference, and pipelined batch reads, plus a background streaming worker (bulk-load, pause/resume, reset, inspect UI).The diff shown includes substantial Go (
featurestorepackage,cmd/demo_server/build_features,demo_server.go) and .NET (ASP.NET minimal API,FeatureStore,StreamingWorker, shared HTML) implementations with explicit handling of per-fieldHEXPIREreply codes, pause +wait_for_idlearound reset, and worker lifecycle. The hub page links nine client ports (Python through Ruby); other languages may land in the same PR beyond the excerpt.Porting skill maintenance: documents the feature-store reference in
redis-use-case-ports, adds audit-checklist rows 35–37 (HEXPIRE/HTTL reply checking, in-flight flag before pause check, bounded worker stop), and a streaming-worker / background-task section inredis-conventions.md(including per-client HEXPIRE pipeline reply shapes).Also lists Feature store on
content/develop/use-cases/_index.mdand broadens.gitignoreto ignore build/vendor output under allcontent/develop/use-cases/**demos (Rust, Java, .NET, PHP, Ruby).Reviewed by Cursor Bugbot for commit 663da47. Bugbot is set up for automated code reviews on this repo. Configure here.