Kong / Kong/developer.konghq.com
Clarify Dedicated Cloud Gateways builtin Redis capabilities
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 121
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 313
Description
Jobs to be done
Based on https://app.kapa.ai/93b55f65-cffb-4d0b-9da7-c8915a838dce/conversations/c85bc4aa-3adb-4ad7-bbde-752eb6714529, determine if the builtin Redis supports vector DB functionality and can be used by AI Gateway semantic policies
This may not be applicable in the 2.0 world depending on how Gateway and AI Gateway do or do not integrate.
Definition of done
Due date (optional)
Size
- S (Small). Example: fixing a broken link, updating wording in an FAQ or paragraph
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Kapa conversation and investigate whether builtin Redis supports vector database functionality for AI Gateway semantic policies. Check whether the Gateway and AI Gateway integration changes this in the 2.0 context. Done means updating that Kapa conversation with the clarified capability and applicability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100