Add LLM banking assistant sample#140
Open
mxsisa wants to merge 2 commits into
Open
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
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.
Sample: Dozer + LLM + Vector database + LangChain banking assistant
This PR adds a runnable sample to getdozer/dozer-samples for the hyper-personalized chatbot use case described in the Dozer blog post about LLMs, vector databases, and LangChain.
What’s included
A new sample at usecases/llm-banking-assistant
dozer-config.yaml sourcing multiple banking datasets from local CSV files
A LangChain app that:
fetches customer context from Dozer REST APIs
retrieves credit card knowledge from a Chroma vector database
sends both into an LLM for personalized recommendations
A reviewer-friendly --dry-run mode that prints the assembled context without requiring an API key
Datasets included:
Dozer views
The sample uses Dozer SQL to build:
eligible_cards
joins customers to cards using annual_income >= min_income
spending_summary
aggregates spend per category
transaction_summary
aggregates transactions per merchant category
Why this addresses the issue:
Issue #1690 asks for a complete working sample based on the blog post’s banking chatbot idea, with:
This sample implements exactly that shape while keeping the setup lightweight for local review.
Implementation notes:
Files added:
Docs update:
Limitations
I could not run a full end-to-end smoke test in this environment because dozer is not installed locally here.