-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi tenant vespa #2762
Multi tenant vespa #2762
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This pull request introduces multi-tenant support for Vespa indexing and search functionality across the Danswer application. Key changes include:
- Added
setup_multitenant_danswer()
andsetup_vespa_multitenant()
functions in/backend/danswer/setup.py
for multi-tenant Vespa index setup - Introduced
tenant_id
field in/backend/danswer/document_index/vespa/app_config/schemas/danswer_chunk.sd
for Vespa schema - Modified
VespaIndex
class in/backend/danswer/document_index/vespa/index.py
to support multi-tenant indexing and improved document deletion - Added
SupportedEmbeddingModel
class in/backend/shared_configs/model_server_models.py
for managing multiple embedding models - Updated search preprocessing in
/backend/danswer/search/preprocessing/preprocessing.py
to include tenant-specific filtering
15 file(s) reviewed, 24 comment(s)
Edit PR Review Bot Settings | Greptile
* k * data -> control * nit * nit: error handling * auth + app * nit: color standardization * nit * nit: typing * k * k * feat: functional upgrading * feat: add block for downgrading to seats < active users * add auth * remove accomplished todo + prints * nit * tiny nit * nit: centralize security * add tenant expulsion/gating + invite user -> increment billing seat no. * add cloud configs * k * k * nit: update
895adc4
to
a01daed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Too long to read it all :| please double check over it and test it thoroughly
Description
[Provide a brief description of the changes in this PR]
How Has This Been Tested?
[Describe the tests you ran to verify your changes]
Accepted Risk
[Any know risks or failure modes to point out to reviewers]
Related Issue(s)
[If applicable, link to the issue(s) this PR addresses]
Checklist: