-
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
Add tenant context #2596
Add tenant context #2596
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
"task": "check_for_vespa_sync_task", | ||
"schedule": timedelta(seconds=5), | ||
"options": {"priority": DanswerCeleryPriority.HIGH}, | ||
"args": (tenant_id,), |
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.
What is the upside/downside of doing this per tenant vs iterating over the tenants in the actual task?
@@ -392,13 +405,35 @@ def kickoff_indexing_jobs( | |||
return existing_jobs_copy | |||
|
|||
|
|||
def get_all_tenant_ids() -> list[str] | list[None]: |
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.
Should we add some prefix for the tenants to double check they're danswer tenants? In case there is other stuff in the DB (which there probably shouldn't be it's better to be safe).
6a7250d
to
b579648
Compare
2247ed3
to
8e92aed
Compare
0cbb679
to
e3424e1
Compare
da194ae
to
90331bd
Compare
bc41ccd
to
e9043ef
Compare
d52a499
to
a4dad03
Compare
Description
Initial addition of tenant context to background processing/tasks